Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7377ea981631bf9cb8d933d047605bf3247b869a7bbfbccf57e25b5a86113d7f

Tx prefix hash: b465dfca087281d29657511f1fb4455befc06015eea8670cde83720d4bb69e9d
Tx public key: 25718ba0f34adf7c3dc016520180ed4a131b2d14fda7f47bb58e49938514e8c8
Timestamp: 1713749771 Timestamp [UCT]: 2024-04-22 01:36:11 Age [y:d:h:m:s]: 00:206:17:21:35
Block: 1005729 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 147993 RingCT/type: yes/0
Extra: 0125718ba0f34adf7c3dc016520180ed4a131b2d14fda7f47bb58e49938514e8c80211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d58d3826f1acd9387b33fcd8f0e51485b7bcc14382e27404b010d9595a7b8840 0.600000000000 1466517 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": 1005739, "vin": [ { "gen": { "height": 1005729 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d58d3826f1acd9387b33fcd8f0e51485b7bcc14382e27404b010d9595a7b8840" } } ], "extra": [ 1, 37, 113, 139, 160, 243, 74, 223, 124, 61, 192, 22, 82, 1, 128, 237, 74, 19, 27, 45, 20, 253, 167, 244, 123, 181, 142, 73, 147, 133, 20, 232, 200, 2, 17, 0, 0, 0, 3, 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