Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4a20d5cabe684de1edc9160808681be450ee79042ed29d76cdda3ef9b6cd0ffc

Tx prefix hash: 3560373aee5402c633773f12d699f1702228e9e53c0285f7425f257eb5696f2b
Tx public key: 735234a6b45e3c02f26ac390dc4861c1627630cc33a26b4ec4cabba2a255fbde
Timestamp: 1697362026 Timestamp [UCT]: 2023-10-15 09:27:06 Age [y:d:h:m:s]: 01:199:23:50:40
Block: 870080 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 403980 RingCT/type: yes/0
Extra: 01735234a6b45e3c02f26ac390dc4861c1627630cc33a26b4ec4cabba2a255fbde02110000000275e3f0e9000000000000000000

1 output(s) for total of 0.803644172000 dcy

stealth address amount amount idx
00: cf9c8778c880a0003f0e930b2a337e82ca98ef26b8bcaf62c8cf61c3299d5702 0.803644172000 1324953 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": 870090, "vin": [ { "gen": { "height": 870080 } } ], "vout": [ { "amount": 803644172, "target": { "key": "cf9c8778c880a0003f0e930b2a337e82ca98ef26b8bcaf62c8cf61c3299d5702" } } ], "extra": [ 1, 115, 82, 52, 166, 180, 94, 60, 2, 242, 106, 195, 144, 220, 72, 97, 193, 98, 118, 48, 204, 51, 162, 107, 78, 196, 202, 187, 162, 162, 85, 251, 222, 2, 17, 0, 0, 0, 2, 117, 227, 240, 233, 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