Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 84708659135f5a020b324e2195a66341f5ee1b586bdc3038f4ad56cc481323b3

Tx prefix hash: f1beb676242b6cdc62da06f8b0cc05612665357f12f2f849969c7772070c583e
Tx public key: 01bc011a36764ece3a54cf8f8cf63df6b9a5d5a8c25bb665838d822ff67afea5
Timestamp: 1766250803 Timestamp [UCT]: 2025-12-20 17:13:23 Age [y:d:h:m:s]: 00:000:18:33:51
Block: 1437870 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 538 RingCT/type: yes/0
Extra: 0101bc011a36764ece3a54cf8f8cf63df6b9a5d5a8c25bb665838d822ff67afea50211000000047b1e51ac000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5305c1a6771f54a84f412a33b9b9ab955f0aebbc18e049cfcb6492de2fdc4f9c 0.600000000000 1926681 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": 1437880, "vin": [ { "gen": { "height": 1437870 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5305c1a6771f54a84f412a33b9b9ab955f0aebbc18e049cfcb6492de2fdc4f9c" } } ], "extra": [ 1, 1, 188, 1, 26, 54, 118, 78, 206, 58, 84, 207, 143, 140, 246, 61, 246, 185, 165, 213, 168, 194, 91, 182, 101, 131, 141, 130, 47, 246, 122, 254, 165, 2, 17, 0, 0, 0, 4, 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