Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 72212c8f7dd12b0d9c5050eb11bb14756eb8b7829ff28b0e58119b31cda6fc4e

Tx prefix hash: 9509129faa9a8ffc2c297e66921e7c1f9a78195610a848748dad55c5ccdde9b9
Tx public key: 743bb723fcef1405eb8f6c6a5d5d9eea8d18a03edcada6a2eb1cea8306fdf9ac
Timestamp: 1721792274 Timestamp [UCT]: 2024-07-24 03:37:54 Age [y:d:h:m:s]: 01:102:08:29:32
Block: 1072404 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 331643 RingCT/type: yes/0
Extra: 01743bb723fcef1405eb8f6c6a5d5d9eea8d18a03edcada6a2eb1cea8306fdf9ac02110000000ce914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 06c6e07726f9ca709ef6e00707d79e359087461c5d25fb8a31c7ac225498935b 0.600000000000 1544873 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": 1072414, "vin": [ { "gen": { "height": 1072404 } } ], "vout": [ { "amount": 600000000, "target": { "key": "06c6e07726f9ca709ef6e00707d79e359087461c5d25fb8a31c7ac225498935b" } } ], "extra": [ 1, 116, 59, 183, 35, 252, 239, 20, 5, 235, 143, 108, 106, 93, 93, 158, 234, 141, 24, 160, 62, 220, 173, 166, 162, 235, 28, 234, 131, 6, 253, 249, 172, 2, 17, 0, 0, 0, 12, 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