Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 354c184efcaefc1bc32efe1be8d662fe597a477876eb115efd0046ef119f2b31

Tx prefix hash: 0fd311b73b668440f599e5a056d11bd2fa8b515a8727790f34f55cc8f7ddc50d
Tx public key: 0378c62fee2837d6d1ae6b06a8f0dcafbd43faa53699ce9f0db89d7ea4952361
Timestamp: 1766248561 Timestamp [UCT]: 2025-12-20 16:36:01 Age [y:d:h:m:s]: 00:001:11:37:49
Block: 1437843 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 1058 RingCT/type: yes/0
Extra: 010378c62fee2837d6d1ae6b06a8f0dcafbd43faa53699ce9f0db89d7ea49523610211000000067b1e51ac000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 78a9ec8ebe8ef0e079ccc3bd7aad330046707ae582404e55db418b4b3d1c906d 0.600000000000 1926654 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": 1437853, "vin": [ { "gen": { "height": 1437843 } } ], "vout": [ { "amount": 600000000, "target": { "key": "78a9ec8ebe8ef0e079ccc3bd7aad330046707ae582404e55db418b4b3d1c906d" } } ], "extra": [ 1, 3, 120, 198, 47, 238, 40, 55, 214, 209, 174, 107, 6, 168, 240, 220, 175, 189, 67, 250, 165, 54, 153, 206, 159, 13, 184, 157, 126, 164, 149, 35, 97, 2, 17, 0, 0, 0, 6, 123, 30, 81, 172, 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