Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dacd25cb1734f09049ee378bde1c1532d8a7e5fb6f29c78ea184cf3ccd6102b9

Tx prefix hash: 3a6df842b6aac7a8fefb85f43910556976ede790e9958cc82fda2bd783a83bbb
Tx public key: aaa2b7b2f385edbebaa81680256059c025bfac3ce3e14138450b4086f9e3e5f2
Timestamp: 1760497860 Timestamp [UCT]: 2025-10-15 03:11:00 Age [y:d:h:m:s]: 00:106:03:29:14
Block: 1390186 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 75818 RingCT/type: yes/0
Extra: 01aaa2b7b2f385edbebaa81680256059c025bfac3ce3e14138450b4086f9e3e5f20211000000012609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0af005bd4386be23882bfcf3d978ea9116281eb457e7a2ec217e03e6c77d181f 0.600000000000 1878417 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": 1390196, "vin": [ { "gen": { "height": 1390186 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0af005bd4386be23882bfcf3d978ea9116281eb457e7a2ec217e03e6c77d181f" } } ], "extra": [ 1, 170, 162, 183, 178, 243, 133, 237, 190, 186, 168, 22, 128, 37, 96, 89, 192, 37, 191, 172, 60, 227, 225, 65, 56, 69, 11, 64, 134, 249, 227, 229, 242, 2, 17, 0, 0, 0, 1, 38, 9, 179, 160, 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