Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e0a171fa9d7bacb46b9f5e9b05d29217c347862f1e1454f1ee557c63872e3ca7

Tx prefix hash: 136a0057ffa90ef3a145263f63d727f1902d074ab1e61e50636319044086c2cb
Tx public key: cf98370067acf786c4aed7807f69ab295c8ce5f492cbc02d6879b426c5a1ee9c
Timestamp: 1720058313 Timestamp [UCT]: 2024-07-04 01:58:33 Age [y:d:h:m:s]: 00:276:09:46:12
Block: 1058042 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 197491 RingCT/type: yes/0
Extra: 01cf98370067acf786c4aed7807f69ab295c8ce5f492cbc02d6879b426c5a1ee9c0211000000010cce0636000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4cfddcfc11e47f8ff529e4ecc66e593f44d08565d7b24c17e789f1d2d72cc33b 0.600000000000 1528487 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": 1058052, "vin": [ { "gen": { "height": 1058042 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4cfddcfc11e47f8ff529e4ecc66e593f44d08565d7b24c17e789f1d2d72cc33b" } } ], "extra": [ 1, 207, 152, 55, 0, 103, 172, 247, 134, 196, 174, 215, 128, 127, 105, 171, 41, 92, 140, 229, 244, 146, 203, 192, 45, 104, 121, 180, 38, 197, 161, 238, 156, 2, 17, 0, 0, 0, 1, 12, 206, 6, 54, 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