Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: d461b5e91b17f06bf96eabc7b21e04872c1accf1b011a287d42eef942fd36681

Tx prefix hash: 640af94f1ec513416148dbcee8d408a8c736cf130b1fb79fa44ca399117e16d7
Tx public key: bb3ac30971facf7cd98cfb5723e4bdc9cdb5f1d9f773c1279af6fda86ad48c38
Timestamp: 1748324081 Timestamp [UCT]: 2025-05-27 05:34:41 Age [y:d:h:m:s]: 00:170:06:51:23
Block: 1291837 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 119390 RingCT/type: yes/0
Extra: 01bb3ac30971facf7cd98cfb5723e4bdc9cdb5f1d9f773c1279af6fda86ad48c3802110000000286ae2f0d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 632ecc284ceda0cf4ae60a619acac36746bf1131e800727df33e1048f21295bf 0.600000000000 1779308 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1291847, "vin": [ { "gen": { "height": 1291837 } } ], "vout": [ { "amount": 600000000, "target": { "key": "632ecc284ceda0cf4ae60a619acac36746bf1131e800727df33e1048f21295bf" } } ], "extra": [ 1, 187, 58, 195, 9, 113, 250, 207, 124, 217, 140, 251, 87, 35, 228, 189, 201, 205, 181, 241, 217, 247, 115, 193, 39, 154, 246, 253, 168, 106, 212, 140, 56, 2, 17, 0, 0, 0, 2, 134, 174, 47, 13, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8