Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0da86fbe95aa283ac902bc543b97125b24595fdf4d691d3ac2a13b80ee95ee25

Tx prefix hash: 5b3dc48b915664092ce1b79c4b4376b7fe1044810dbe7f6ff63b64617a700ce2
Tx public key: 7acf669e1bf34ea5e449fd693d8757393d6e4c2c86477d33e1f5d6ba139cd4da
Timestamp: 1743885283 Timestamp [UCT]: 2025-04-05 20:34:43 Age [y:d:h:m:s]: 00:227:17:33:50
Block: 1255078 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 160493 RingCT/type: yes/0
Extra: 017acf669e1bf34ea5e449fd693d8757393d6e4c2c86477d33e1f5d6ba139cd4da0211000000016c98aa3d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 748aa016f2cc20144e01a1891ab8c41115183684d5bcf7c13eca653ecde31623 0.600000000000 1742181 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": 1255088, "vin": [ { "gen": { "height": 1255078 } } ], "vout": [ { "amount": 600000000, "target": { "key": "748aa016f2cc20144e01a1891ab8c41115183684d5bcf7c13eca653ecde31623" } } ], "extra": [ 1, 122, 207, 102, 158, 27, 243, 78, 165, 228, 73, 253, 105, 61, 135, 87, 57, 61, 110, 76, 44, 134, 71, 125, 51, 225, 245, 214, 186, 19, 156, 212, 218, 2, 17, 0, 0, 0, 1, 108, 152, 170, 61, 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