Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 39298c181c1de5944200896273564595ed2c7d6ac1d3974b37a84459453244de

Tx prefix hash: a268efab6d7d480fc83559bb9556dc2cd2cbb730adc9a2722703da9b03dc6c69
Tx public key: 7fbd0bd274032a6b8a841929437378c7b01d2146c7cdc666b47ba08df3dc7d48
Timestamp: 1705488009 Timestamp [UCT]: 2024-01-17 10:40:09 Age [y:d:h:m:s]: 01:299:22:32:05
Block: 937223 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 473187 RingCT/type: yes/0
Extra: 017fbd0bd274032a6b8a841929437378c7b01d2146c7cdc666b47ba08df3dc7d480211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f439f91b2377a427ef6373e3c3a8be35dac8a76f1217067ee7ecdda71fe7acd8 0.600000000000 1395267 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": 937233, "vin": [ { "gen": { "height": 937223 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f439f91b2377a427ef6373e3c3a8be35dac8a76f1217067ee7ecdda71fe7acd8" } } ], "extra": [ 1, 127, 189, 11, 210, 116, 3, 42, 107, 138, 132, 25, 41, 67, 115, 120, 199, 176, 29, 33, 70, 199, 205, 198, 102, 180, 123, 160, 141, 243, 220, 125, 72, 2, 17, 0, 0, 0, 4, 122, 156, 244, 199, 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