Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 861845fd72e8ff59ee3ca5ee46f12b8a2ddbfb531b4371698423f7c5d65b583d

Tx prefix hash: 43429f60461c8f2a6c7a85859727c403ab2fddd345c1d5415bb0473c1c4d18e8
Tx public key: 5031696d3f11fff82ccb8fc8129efa4a71de5f9fa8407afd49bca03f63d435ca
Timestamp: 1765616105 Timestamp [UCT]: 2025-12-13 08:55:05 Age [y:d:h:m:s]: 00:009:01:50:19
Block: 1432612 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 6485 RingCT/type: yes/0
Extra: 015031696d3f11fff82ccb8fc8129efa4a71de5f9fa8407afd49bca03f63d435ca021100000001d6e19d7c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 160fb452cd89d8c0726a8b6260c648e3c9327d08ed5c01c261ed512cde2d2016 0.600000000000 1921391 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": 1432622, "vin": [ { "gen": { "height": 1432612 } } ], "vout": [ { "amount": 600000000, "target": { "key": "160fb452cd89d8c0726a8b6260c648e3c9327d08ed5c01c261ed512cde2d2016" } } ], "extra": [ 1, 80, 49, 105, 109, 63, 17, 255, 248, 44, 203, 143, 200, 18, 158, 250, 74, 113, 222, 95, 159, 168, 64, 122, 253, 73, 188, 160, 63, 99, 212, 53, 202, 2, 17, 0, 0, 0, 1, 214, 225, 157, 124, 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