Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4a5bf39407bc76efc1e95521b92f67b491bcbb56eb2538faffd87ce4dcfdddbb

Tx prefix hash: abc6c233f1437685c0b50a7216efd8fb87b4f51b72af2a11a7f3082a12532226
Tx public key: 323b95503b2452fb96b30def7b63bf023b5c43b1c92861d63a8d041476f1e233
Timestamp: 1708598080 Timestamp [UCT]: 2024-02-22 10:34:40 Age [y:d:h:m:s]: 01:117:13:13:59
Block: 963027 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 344949 RingCT/type: yes/0
Extra: 01323b95503b2452fb96b30def7b63bf023b5c43b1c92861d63a8d041476f1e23302110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4176c32a7d36d41d5c70b8eeb5ded46614ecbb6f0a58f8d5bf94ebbda783662b 0.600000000000 1422724 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": 963037, "vin": [ { "gen": { "height": 963027 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4176c32a7d36d41d5c70b8eeb5ded46614ecbb6f0a58f8d5bf94ebbda783662b" } } ], "extra": [ 1, 50, 59, 149, 80, 59, 36, 82, 251, 150, 179, 13, 239, 123, 99, 191, 2, 59, 92, 67, 177, 201, 40, 97, 214, 58, 141, 4, 20, 118, 241, 226, 51, 2, 17, 0, 0, 0, 3, 89, 218, 211, 245, 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