Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 91475acc7d9808fd60d5b2477a000ef8597172bf2f75a6cf2d8e362dd2575edb

Tx prefix hash: e6ae9409d8eef9d6003b532280520dbecbe141cf31d7b21dfa2a2da8f9701adb
Tx public key: e243ba819b2ee3a7f9f361e148d4db91c7a2bb128cd357a9b6a600f3adf86493
Timestamp: 1731423020 Timestamp [UCT]: 2024-11-12 14:50:20 Age [y:d:h:m:s]: 00:139:07:32:53
Block: 1152170 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 99384 RingCT/type: yes/0
Extra: 01e243ba819b2ee3a7f9f361e148d4db91c7a2bb128cd357a9b6a600f3adf864930211000000071f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 56da30e02c28cfceb8e41d653c0442fcc25d23a0590367accbc8644b6d7b650a 0.600000000000 1637761 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": 1152180, "vin": [ { "gen": { "height": 1152170 } } ], "vout": [ { "amount": 600000000, "target": { "key": "56da30e02c28cfceb8e41d653c0442fcc25d23a0590367accbc8644b6d7b650a" } } ], "extra": [ 1, 226, 67, 186, 129, 155, 46, 227, 167, 249, 243, 97, 225, 72, 212, 219, 145, 199, 162, 187, 18, 140, 211, 87, 169, 182, 166, 0, 243, 173, 248, 100, 147, 2, 17, 0, 0, 0, 7, 31, 10, 83, 235, 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