Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 01107fc1cdece0d01fdea01b269024bfa1b2a9693d4691a982c85b69c69ba559

Tx prefix hash: 50c1acde7885cba5e9f23d2f76adbe3540cdbaa5d84132ba6bb73bf02587a231
Tx public key: 0455002fcac771e51f4494c08df848206677bfb488354d79df503c6c4ca9aa27
Timestamp: 1648233816 Timestamp [UCT]: 2022-03-25 18:43:36 Age [y:d:h:m:s]: 03:220:11:34:27
Block: 466278 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 935467 RingCT/type: yes/0
Extra: 010455002fcac771e51f4494c08df848206677bfb488354d79df503c6c4ca9aa27021100000005a272b9cb000000000000000000

1 output(s) for total of 17.499582185000 dcy

stealth address amount amount idx
00: dae65ea22cb16d7921135a41b83e841c5d73c8d5efd202843a6231a76b1a2a74 17.499582185000 884561 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": 466288, "vin": [ { "gen": { "height": 466278 } } ], "vout": [ { "amount": 17499582185, "target": { "key": "dae65ea22cb16d7921135a41b83e841c5d73c8d5efd202843a6231a76b1a2a74" } } ], "extra": [ 1, 4, 85, 0, 47, 202, 199, 113, 229, 31, 68, 148, 192, 141, 248, 72, 32, 102, 119, 191, 180, 136, 53, 77, 121, 223, 80, 60, 108, 76, 169, 170, 39, 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