Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ac6935f677366e717254c329f412d7d3f4add6b2267c71d7707c1263976f4a30

Tx prefix hash: f3412e28ffdbb48d42ec4af310d0df2ab4bc8f0bee32a8e7c00c025fb040004e
Tx public key: 52d33647dc1b64db6dd20920ceafdce8f4811958abb50ab7c0ea2594f2fdc531
Timestamp: 1721234848 Timestamp [UCT]: 2024-07-17 16:47:28 Age [y:d:h:m:s]: 00:129:15:28:11
Block: 1067806 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 92753 RingCT/type: yes/0
Extra: 0152d33647dc1b64db6dd20920ceafdce8f4811958abb50ab7c0ea2594f2fdc53102110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e8de57af79b48cb588fe359f71618714a6a6c9a9fee60886adfcbeea97f389b3 0.600000000000 1538721 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": 1067816, "vin": [ { "gen": { "height": 1067806 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e8de57af79b48cb588fe359f71618714a6a6c9a9fee60886adfcbeea97f389b3" } } ], "extra": [ 1, 82, 211, 54, 71, 220, 27, 100, 219, 109, 210, 9, 32, 206, 175, 220, 232, 244, 129, 25, 88, 171, 181, 10, 183, 192, 234, 37, 148, 242, 253, 197, 49, 2, 17, 0, 0, 0, 3, 145, 225, 60, 4, 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