Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cf1a7dcccfafde2b027c688e32fe7ab3a1350973bdaf70f12d933f9abc254253

Tx prefix hash: f0e0a08f407ccd518cf3dd906d3fc00fec57dd741909e05870bc7f886ed1fead
Tx public key: 5d07cda735cca2e99a1fdb4f898f94fe1fdcde3bca5451dc4dab8741b5a01913
Timestamp: 1727662968 Timestamp [UCT]: 2024-09-30 02:22:48 Age [y:d:h:m:s]: 00:261:11:48:12
Block: 1121085 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 186611 RingCT/type: yes/0
Extra: 015d07cda735cca2e99a1fdb4f898f94fe1fdcde3bca5451dc4dab8741b5a0191302110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d03e9abb22c83f299432533b92d557cacedeca8544f4a8ff4702641f8d9c0ce3 0.600000000000 1603232 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": 1121095, "vin": [ { "gen": { "height": 1121085 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d03e9abb22c83f299432533b92d557cacedeca8544f4a8ff4702641f8d9c0ce3" } } ], "extra": [ 1, 93, 7, 205, 167, 53, 204, 162, 233, 154, 31, 219, 79, 137, 143, 148, 254, 31, 220, 222, 59, 202, 84, 81, 220, 77, 171, 135, 65, 181, 160, 25, 19, 2, 17, 0, 0, 0, 4, 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