Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fd780995b1ae4aa3c36106da34b24d00f656db2e43b491eed66223572250f63b

Tx prefix hash: 6682883b14f52bc78b83d01204f8a3757c151cd833e719a299d1811d0292b912
Tx public key: baa7894640b34060cfda8d3d778540fb3d99e5e525d4b3d684f497545c3af0f8
Timestamp: 1727786437 Timestamp [UCT]: 2024-10-01 12:40:37 Age [y:d:h:m:s]: 00:189:22:59:59
Block: 1122112 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 135571 RingCT/type: yes/0
Extra: 01baa7894640b34060cfda8d3d778540fb3d99e5e525d4b3d684f497545c3af0f802110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8da5da9391d68b0f57ac833cad8e8e1ae537580fc7f4ae9620f2f0539001823d 0.600000000000 1604493 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": 1122122, "vin": [ { "gen": { "height": 1122112 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8da5da9391d68b0f57ac833cad8e8e1ae537580fc7f4ae9620f2f0539001823d" } } ], "extra": [ 1, 186, 167, 137, 70, 64, 179, 64, 96, 207, 218, 141, 61, 119, 133, 64, 251, 61, 153, 229, 229, 37, 212, 179, 214, 132, 244, 151, 84, 92, 58, 240, 248, 2, 17, 0, 0, 0, 2, 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