Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d4dcee1e1e6c05b9168cb0c6d3887e5773b6aa23215dc56f3569f063ca575d07

Tx prefix hash: cee41aa897a643eb91030d0c7683c6169b402d97e662717a1345f5c51c9daff8
Tx public key: 685b24bb2527119f32f776cd41eb27795bc1cbd76baf11419c230dd350251d01
Timestamp: 1643409032 Timestamp [UCT]: 2022-01-28 22:30:32 Age [y:d:h:m:s]: 03:011:20:50:49
Block: 427357 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 787637 RingCT/type: yes/0
Extra: 01685b24bb2527119f32f776cd41eb27795bc1cbd76baf11419c230dd350251d01021100000005a272b9cb000000000000000000

1 output(s) for total of 23.549905384000 dcy

stealth address amount amount idx
00: c3bee9a2d18f333991dc15f960f4daa7c665a3f2e242c8c7556ed7a79b15cd9d 23.549905384000 836469 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": 427367, "vin": [ { "gen": { "height": 427357 } } ], "vout": [ { "amount": 23549905384, "target": { "key": "c3bee9a2d18f333991dc15f960f4daa7c665a3f2e242c8c7556ed7a79b15cd9d" } } ], "extra": [ 1, 104, 91, 36, 187, 37, 39, 17, 159, 50, 247, 118, 205, 65, 235, 39, 121, 91, 193, 203, 215, 107, 175, 17, 65, 156, 35, 13, 211, 80, 37, 29, 1, 2, 17, 0, 0, 0, 5, 162, 114, 185, 203, 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