Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 308f7450112962afc43a2ca24f033eaa351e82763d3cc0540066f8fb033debbf

Tx prefix hash: a01578c29859b387aa3cd583f97cddfd57321ccf6cebb2c9f07ad71b6e95bf44
Tx public key: e05d317b73e59f84a0d45cf9a30cde2b6015d24c63470f01a14af8c164e7b733
Timestamp: 1717207260 Timestamp [UCT]: 2024-06-01 02:01:00 Age [y:d:h:m:s]: 00:209:01:00:43
Block: 1034407 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 149598 RingCT/type: yes/0
Extra: 01e05d317b73e59f84a0d45cf9a30cde2b6015d24c63470f01a14af8c164e7b73302110000000559dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: de7cfe0a241f598c149484a8418641c58c6ae4675b663a839bd75d4d802e1b32 0.600000000000 1502916 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": 1034417, "vin": [ { "gen": { "height": 1034407 } } ], "vout": [ { "amount": 600000000, "target": { "key": "de7cfe0a241f598c149484a8418641c58c6ae4675b663a839bd75d4d802e1b32" } } ], "extra": [ 1, 224, 93, 49, 123, 115, 229, 159, 132, 160, 212, 92, 249, 163, 12, 222, 43, 96, 21, 210, 76, 99, 71, 15, 1, 161, 74, 248, 193, 100, 231, 183, 51, 2, 17, 0, 0, 0, 5, 89, 218, 211, 245, 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