Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1cf070fe6ac837aa6faf8096e98c90ecd814f64c269cdb3e735af6a9f4e8f587

Tx prefix hash: 34dccf7ddc89c4e4a0d98c6d6755f184b72fe4d01cc2f48ba17156ce673b1833
Tx public key: 22e252e80d3cc33ad05fd67a77de6cdb87e9a78f73f397e8405a6046051296fa
Timestamp: 1733207307 Timestamp [UCT]: 2024-12-03 06:28:27 Age [y:d:h:m:s]: 00:140:17:29:27
Block: 1166946 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 100382 RingCT/type: yes/0
Extra: 0122e252e80d3cc33ad05fd67a77de6cdb87e9a78f73f397e8405a6046051296fa0211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a0f4b0a4cd950582e73a7108251f5ff5d0020862680a8736ee4f91962d97be45 0.600000000000 1652639 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": 1166956, "vin": [ { "gen": { "height": 1166946 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a0f4b0a4cd950582e73a7108251f5ff5d0020862680a8736ee4f91962d97be45" } } ], "extra": [ 1, 34, 226, 82, 232, 13, 60, 195, 58, 208, 95, 214, 122, 119, 222, 108, 219, 135, 233, 167, 143, 115, 243, 151, 232, 64, 90, 96, 70, 5, 18, 150, 250, 2, 17, 0, 0, 0, 4, 31, 10, 83, 235, 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