Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: aaa07fb1bde9b31736ad6c6a6e85b46970f1104b76c4d4ba1eb868cd83928da4

Tx prefix hash: dfed1d3239d68d283d8064fdf539f42d9acd3a50ba966bc36c36338d0c691ca6
Tx public key: 0956a13a79aba26da2e1b8da4289cdafbdf311a8c5e23a17311cd752308fc656
Timestamp: 1712093787 Timestamp [UCT]: 2024-04-02 21:36:27 Age [y:d:h:m:s]: 01:038:12:11:57
Block: 991976 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 288536 RingCT/type: yes/0
Extra: 010956a13a79aba26da2e1b8da4289cdafbdf311a8c5e23a17311cd752308fc6560211000000067a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3a8a774e2e1035e791e75226befe6a6f1687c63e1cdea724ab44c95bb69d7b67 0.600000000000 1452312 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": 991986, "vin": [ { "gen": { "height": 991976 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3a8a774e2e1035e791e75226befe6a6f1687c63e1cdea724ab44c95bb69d7b67" } } ], "extra": [ 1, 9, 86, 161, 58, 121, 171, 162, 109, 162, 225, 184, 218, 66, 137, 205, 175, 189, 243, 17, 168, 197, 226, 58, 23, 49, 28, 215, 82, 48, 143, 198, 86, 2, 17, 0, 0, 0, 6, 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