Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a44fcb7a559bb1b0266d520385e513c8a190a64d7ed0bcfad08a315e6175b711

Tx prefix hash: 32ca52c57a21556c90472db245160e5e663209285dd6f8e6d4739a31d3b85914
Tx public key: 10f7d97664f1f9041dba88be28955e4f114958b4e5832901c51ee325e9face4b
Timestamp: 1698515594 Timestamp [UCT]: 2023-10-28 17:53:14 Age [y:d:h:m:s]: 01:163:17:47:22
Block: 879655 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 378028 RingCT/type: yes/0
Extra: 0110f7d97664f1f9041dba88be28955e4f114958b4e5832901c51ee325e9face4b021100000008e6d27f9c000000000000000000

1 output(s) for total of 0.747029644000 dcy

stealth address amount amount idx
00: d7eecb0b81e26e79d4eb44f23f85ae6c58cbb4be6ef7a632666003a70541ce00 0.747029644000 1335189 of 0

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": 879665, "vin": [ { "gen": { "height": 879655 } } ], "vout": [ { "amount": 747029644, "target": { "key": "d7eecb0b81e26e79d4eb44f23f85ae6c58cbb4be6ef7a632666003a70541ce00" } } ], "extra": [ 1, 16, 247, 217, 118, 100, 241, 249, 4, 29, 186, 136, 190, 40, 149, 94, 79, 17, 73, 88, 180, 229, 131, 41, 1, 197, 30, 227, 37, 233, 250, 206, 75, 2, 17, 0, 0, 0, 8, 230, 210, 127, 156, 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