Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 986d397d853778357b258c9dd4fb0112642e27b19765f371aaa8b54bd14aae21

Tx prefix hash: 795fb13c78c66e4eaccde7727b97b053fd4cae8fd51bc4414d41d1f5224a1c5f
Tx public key: f8092da8bef67af0baf4914becadd34873b616ea278a9eecd5bed3b1eeee8933
Timestamp: 1694044110 Timestamp [UCT]: 2023-09-06 23:48:30 Age [y:d:h:m:s]: 01:139:00:19:01
Block: 842542 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 360655 RingCT/type: yes/0
Extra: 01f8092da8bef67af0baf4914becadd34873b616ea278a9eecd5bed3b1eeee893302110000000a4b8f5122000000000000000000

1 output(s) for total of 0.991536408000 dcy

stealth address amount amount idx
00: 4430dd319f425be97978ac1c71bdd501bdf58da6b46847ae87f30f1ed80d26b6 0.991536408000 1295672 of 0

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": 842552, "vin": [ { "gen": { "height": 842542 } } ], "vout": [ { "amount": 991536408, "target": { "key": "4430dd319f425be97978ac1c71bdd501bdf58da6b46847ae87f30f1ed80d26b6" } } ], "extra": [ 1, 248, 9, 45, 168, 190, 246, 122, 240, 186, 244, 145, 75, 236, 173, 211, 72, 115, 182, 22, 234, 39, 138, 158, 236, 213, 190, 211, 177, 238, 238, 137, 51, 2, 17, 0, 0, 0, 10, 75, 143, 81, 34, 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