Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 270bad366b4c3b4fbed6780313fe5a16bac6ee7c7246d8a0c3ee24e05419d2b2

Tx prefix hash: 8192e9a760fb4be4a72cb90d3ae951e8651740927d1a24ae57856a3e2be2d131
Tx public key: fb166d88c1a5f80c0258fa55dec5df849ecb19f3b8a548d2cc2bef081a6a7bfc
Timestamp: 1724611142 Timestamp [UCT]: 2024-08-25 18:39:02 Age [y:d:h:m:s]: 00:223:21:02:14
Block: 1095788 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 159853 RingCT/type: yes/0
Extra: 01fb166d88c1a5f80c0258fa55dec5df849ecb19f3b8a548d2cc2bef081a6a7bfc02110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 87466fa8a4d8b54c7f64a3991834a59a0b66ee42380e47f9837a5a1a87c1daa5 0.600000000000 1570971 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": 1095798, "vin": [ { "gen": { "height": 1095788 } } ], "vout": [ { "amount": 600000000, "target": { "key": "87466fa8a4d8b54c7f64a3991834a59a0b66ee42380e47f9837a5a1a87c1daa5" } } ], "extra": [ 1, 251, 22, 109, 136, 193, 165, 248, 12, 2, 88, 250, 85, 222, 197, 223, 132, 158, 203, 25, 243, 184, 165, 72, 210, 204, 43, 239, 8, 26, 106, 123, 252, 2, 17, 0, 0, 0, 5, 145, 225, 60, 4, 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