Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cf4892d801529f41bed962f837863cbf6d0f3901d4a485bc53c92c61ce125794

Tx prefix hash: 5dbf699ad9e8c189f8976fe59fe943a4430e4158ce94d7f5a3a3969734b53485
Tx public key: 51b4b9a5d9afce56b1467376dc3910bf4e4d2f3cf5f7f68e9e6904bfe2ff74a8
Timestamp: 1745146146 Timestamp [UCT]: 2025-04-20 10:49:06 Age [y:d:h:m:s]: 00:286:23:37:43
Block: 1265514 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 202751 RingCT/type: yes/0
Extra: 0151b4b9a5d9afce56b1467376dc3910bf4e4d2f3cf5f7f68e9e6904bfe2ff74a80211000000066c98aa3d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 57fd13721ed10994d5164e143ac3383bebcbcdb08790d85bb0bd1dfe57d2fc97 0.600000000000 1752725 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": 1265524, "vin": [ { "gen": { "height": 1265514 } } ], "vout": [ { "amount": 600000000, "target": { "key": "57fd13721ed10994d5164e143ac3383bebcbcdb08790d85bb0bd1dfe57d2fc97" } } ], "extra": [ 1, 81, 180, 185, 165, 217, 175, 206, 86, 177, 70, 115, 118, 220, 57, 16, 191, 78, 77, 47, 60, 245, 247, 246, 142, 158, 105, 4, 191, 226, 255, 116, 168, 2, 17, 0, 0, 0, 6, 108, 152, 170, 61, 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