Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5d3eb66501e140a6033644e5edc13bbbc4b9967bfc283e76a8fe5e82de3f70d8

Tx prefix hash: a6e03092f2d0c380620710947d8a078b8b83d3bd1f30cd40a7ae9bd6d7072ea6
Tx public key: a733aaccaa9276677433806005a422113be1aca6e8c806c6d125a48bb05aeffe
Timestamp: 1724000220 Timestamp [UCT]: 2024-08-18 16:57:00 Age [y:d:h:m:s]: 00:229:02:59:28
Block: 1090723 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 163615 RingCT/type: yes/0
Extra: 01a733aaccaa9276677433806005a422113be1aca6e8c806c6d125a48bb05aeffe02110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f48ebb50ea0e5cd8bfb2c2aa39f827bf0315c22a7c0e7414d28467c7584014d6 0.600000000000 1565346 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": 1090733, "vin": [ { "gen": { "height": 1090723 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f48ebb50ea0e5cd8bfb2c2aa39f827bf0315c22a7c0e7414d28467c7584014d6" } } ], "extra": [ 1, 167, 51, 170, 204, 170, 146, 118, 103, 116, 51, 128, 96, 5, 164, 34, 17, 59, 225, 172, 166, 232, 200, 6, 198, 209, 37, 164, 139, 176, 90, 239, 254, 2, 17, 0, 0, 0, 3, 145, 225, 60, 4, 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