Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 588171bc2c77af87e489e5123e0d2f238c49844d5ff20079b0dc61067d060891

Tx prefix hash: 0311530578a6f5acd692eb54f95f8f3a1a4f32039aed10d9b52905c6bb80cb61
Tx public key: 3087ae49e3571144d75b38d21583159671303b8f75b593f2a0405ad0ab4c8471
Timestamp: 1726048294 Timestamp [UCT]: 2024-09-11 09:51:34 Age [y:d:h:m:s]: 00:264:23:33:15
Block: 1107703 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 189268 RingCT/type: yes/0
Extra: 013087ae49e3571144d75b38d21583159671303b8f75b593f2a0405ad0ab4c8471021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ec0962ae3703718805ae6253f21a01a877af017c8c8f18ac953e9c001ed9f67e 0.600000000000 1585332 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": 1107713, "vin": [ { "gen": { "height": 1107703 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ec0962ae3703718805ae6253f21a01a877af017c8c8f18ac953e9c001ed9f67e" } } ], "extra": [ 1, 48, 135, 174, 73, 227, 87, 17, 68, 215, 91, 56, 210, 21, 131, 21, 150, 113, 48, 59, 143, 117, 181, 147, 242, 160, 64, 90, 208, 171, 76, 132, 113, 2, 17, 0, 0, 0, 1, 233, 20, 221, 21, 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