Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b8ee66900a223d0fe38b7552fa5d46f16d8d0e1ad72ce2dd6de510f2078e4923

Tx prefix hash: 173593faf8890990b2997a5f04ecb44425575cfdf07f581dfecc37a902297a0a
Tx public key: b4759cb86ef528e7075a95d3ee378d613df563d6636bc3fe24e7f8546e478836
Timestamp: 1681137011 Timestamp [UCT]: 2023-04-10 14:30:11 Age [y:d:h:m:s]: 01:285:14:49:51
Block: 735598 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 465608 RingCT/type: yes/0
Extra: 01b4759cb86ef528e7075a95d3ee378d613df563d6636bc3fe24e7f8546e478836021100000002b3164c24000000000000000000

1 output(s) for total of 2.242119155000 dcy

stealth address amount amount idx
00: ba266d7fa2c3ceb2bd000b0b7f457f8a9c1d871b7114646fe88cf0a03818d904 2.242119155000 1181941 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": 735608, "vin": [ { "gen": { "height": 735598 } } ], "vout": [ { "amount": 2242119155, "target": { "key": "ba266d7fa2c3ceb2bd000b0b7f457f8a9c1d871b7114646fe88cf0a03818d904" } } ], "extra": [ 1, 180, 117, 156, 184, 110, 245, 40, 231, 7, 90, 149, 211, 238, 55, 141, 97, 61, 245, 99, 214, 99, 107, 195, 254, 36, 231, 248, 84, 110, 71, 136, 54, 2, 17, 0, 0, 0, 2, 179, 22, 76, 36, 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