Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2d3bae4a4633dcdbad4ed00cb3d5216c12decb317cb4e52405836a79ba88a880

Tx prefix hash: 9ab283ac0dafc43f8eef6e912a5791c96eaa6b9ef27531fa94260d801886dd59
Tx public key: 9c5332ed3896c2a5e2ffee38ca970cfd34a35d61032a1ec6b59cf2859ffb8d08
Timestamp: 1764115863 Timestamp [UCT]: 2025-11-26 00:11:03 Age [y:d:h:m:s]: 00:027:05:52:43
Block: 1420174 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 19496 RingCT/type: yes/0
Extra: 019c5332ed3896c2a5e2ffee38ca970cfd34a35d61032a1ec6b59cf2859ffb8d08021100000001defb8f18000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3fd59879fef692e77e5aaf7184eb9f41095a35b04125dfc18423aa08ab18f922 0.600000000000 1908715 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": 1420184, "vin": [ { "gen": { "height": 1420174 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3fd59879fef692e77e5aaf7184eb9f41095a35b04125dfc18423aa08ab18f922" } } ], "extra": [ 1, 156, 83, 50, 237, 56, 150, 194, 165, 226, 255, 238, 56, 202, 151, 12, 253, 52, 163, 93, 97, 3, 42, 30, 198, 181, 156, 242, 133, 159, 251, 141, 8, 2, 17, 0, 0, 0, 1, 222, 251, 143, 24, 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