Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 848e92446ab8b4a26786e6c3175ee4c6b401b6e3aaa591e436a81cb5dd204eae

Tx prefix hash: 7f361a828b1d9fcd07829f28172abadf7741c75f8711fce4b682108f427d0cb3
Tx public key: d451452ce7d338c45e7c77c17177c79af7457a62683ada3d06f990b6bdc3a9c4
Timestamp: 1745734560 Timestamp [UCT]: 2025-04-27 06:16:00 Age [y:d:h:m:s]: 00:207:01:45:29
Block: 1270389 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 145716 RingCT/type: yes/0
Extra: 01d451452ce7d338c45e7c77c17177c79af7457a62683ada3d06f990b6bdc3a9c402110000000201491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9c6c918a40b3fa36f3d0d507724756ce8fa353fe1b336a1b7de76d99cf83fdca 0.600000000000 1757632 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": 1270399, "vin": [ { "gen": { "height": 1270389 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9c6c918a40b3fa36f3d0d507724756ce8fa353fe1b336a1b7de76d99cf83fdca" } } ], "extra": [ 1, 212, 81, 69, 44, 231, 211, 56, 196, 94, 124, 119, 193, 113, 119, 199, 154, 247, 69, 122, 98, 104, 58, 218, 61, 6, 249, 144, 182, 189, 195, 169, 196, 2, 17, 0, 0, 0, 2, 1, 73, 31, 136, 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