Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bf6258a3c2f1c74b48b4ae8c16e11cdbd8f012186b3f5b8830b7a2842782d7d0

Tx prefix hash: 301c4c25a99e3a36ae32e90916c7353d48a59c96d42a6c6e1e179a8145b80b5c
Tx public key: a399c190ce170445ea35451f61e5ab4b62fe8bf4004010196e74271234b36888
Timestamp: 1717690395 Timestamp [UCT]: 2024-06-06 16:13:15 Age [y:d:h:m:s]: 00:216:10:29:43
Block: 1038409 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 154899 RingCT/type: yes/0
Extra: 01a399c190ce170445ea35451f61e5ab4b62fe8bf4004010196e74271234b3688802110000000559dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 99055991dc0eb83e8d1b90ee114ecfb1b5eebba26d99a657555f14ddeb4f69cf 0.600000000000 1506970 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": 1038419, "vin": [ { "gen": { "height": 1038409 } } ], "vout": [ { "amount": 600000000, "target": { "key": "99055991dc0eb83e8d1b90ee114ecfb1b5eebba26d99a657555f14ddeb4f69cf" } } ], "extra": [ 1, 163, 153, 193, 144, 206, 23, 4, 69, 234, 53, 69, 31, 97, 229, 171, 75, 98, 254, 139, 244, 0, 64, 16, 25, 110, 116, 39, 18, 52, 179, 104, 136, 2, 17, 0, 0, 0, 5, 89, 218, 211, 245, 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