Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 81b4339f732277e455e0b402f0caf286f91753c6c78db437e224cb89bfcfea02

Tx prefix hash: 5ef5e9baf994945921766f33a729ba10ed4b68a6464f2c56883420ebaed4f45a
Tx public key: 2308ac06e9547e66a90907d81c6d4563b75928715df438ee976fdb3e0aa50436
Timestamp: 1711389698 Timestamp [UCT]: 2024-03-25 18:01:38 Age [y:d:h:m:s]: 00:291:02:09:39
Block: 986196 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 208341 RingCT/type: yes/0
Extra: 012308ac06e9547e66a90907d81c6d4563b75928715df438ee976fdb3e0aa5043602110000000552d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e9262cf4d080917b66468547c9b7ae21150f7b1c12b7e55ef5e4a21d6cb3531f 0.600000000000 1446423 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": 986206, "vin": [ { "gen": { "height": 986196 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e9262cf4d080917b66468547c9b7ae21150f7b1c12b7e55ef5e4a21d6cb3531f" } } ], "extra": [ 1, 35, 8, 172, 6, 233, 84, 126, 102, 169, 9, 7, 216, 28, 109, 69, 99, 183, 89, 40, 113, 93, 244, 56, 238, 151, 111, 219, 62, 10, 165, 4, 54, 2, 17, 0, 0, 0, 5, 82, 212, 126, 148, 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