Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: db60fd05c3313a280dc15b415ae0333914a47ebb438f4a8df8c05b9f6502e9d6

Tx prefix hash: d23b7c9407ff5ed78c530fc9e9acf13533d8f0dbc95353b8020a2bb5225d3ad8
Tx public key: e03904d961a4bad63dededa92cf7e787d06f20223229aea6550326dc5d746ed2
Timestamp: 1702385180 Timestamp [UCT]: 2023-12-12 12:46:20 Age [y:d:h:m:s]: 01:132:14:57:56
Block: 911537 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 355911 RingCT/type: yes/0
Extra: 01e03904d961a4bad63dededa92cf7e787d06f20223229aea6550326dc5d746ed202110000000975e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 458a1bc8ae2fde2183b8328aa3154b8b4be76b673214245a0fb850be0bfba10b 0.600000000000 1368741 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": 911547, "vin": [ { "gen": { "height": 911537 } } ], "vout": [ { "amount": 600000000, "target": { "key": "458a1bc8ae2fde2183b8328aa3154b8b4be76b673214245a0fb850be0bfba10b" } } ], "extra": [ 1, 224, 57, 4, 217, 97, 164, 186, 214, 61, 237, 237, 169, 44, 247, 231, 135, 208, 111, 32, 34, 50, 41, 174, 166, 85, 3, 38, 220, 93, 116, 110, 210, 2, 17, 0, 0, 0, 9, 117, 227, 240, 233, 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