Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1a669ec24792e6e093ac4894fb6eb232e456ca8ae8c49aff2f17eb01312c4bf3

Tx prefix hash: 51fffd60a191468eb8ce523f352c7634bffcdbc5e037bdc8a1229de8c75a789f
Tx public key: 8faca9a7c0bbe75e61ff1e33ea57ac0b748b957aa4ffce7310f5262956ebaa0b
Timestamp: 1721714439 Timestamp [UCT]: 2024-07-23 06:00:39 Age [y:d:h:m:s]: 00:295:16:26:48
Block: 1071759 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 211281 RingCT/type: yes/0
Extra: 018faca9a7c0bbe75e61ff1e33ea57ac0b748b957aa4ffce7310f5262956ebaa0b02110000000f91e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 37ee3dca875934068c27e87b158ad2788c120c5fc53da7c3e0926114549f1257 0.600000000000 1544106 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": 1071769, "vin": [ { "gen": { "height": 1071759 } } ], "vout": [ { "amount": 600000000, "target": { "key": "37ee3dca875934068c27e87b158ad2788c120c5fc53da7c3e0926114549f1257" } } ], "extra": [ 1, 143, 172, 169, 167, 192, 187, 231, 94, 97, 255, 30, 51, 234, 87, 172, 11, 116, 139, 149, 122, 164, 255, 206, 115, 16, 245, 38, 41, 86, 235, 170, 11, 2, 17, 0, 0, 0, 15, 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