Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 096189552fd11bb359460b6b52499a7322f0e838d2e73bd690a4effe085e417f

Tx prefix hash: 561da9c15620ccc2b19f7fb0aaf7747b906c9dba5a0be3085ebbb3d1aacb7de4
Tx public key: 1a23eb25139b2e575374cb68fd846765916aec14f6035bcad09a4077d45446c6
Timestamp: 1679440552 Timestamp [UCT]: 2023-03-21 23:15:52 Age [y:d:h:m:s]: 02:235:01:59:01
Block: 722199 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 687258 RingCT/type: yes/0
Extra: 011a23eb25139b2e575374cb68fd846765916aec14f6035bcad09a4077d45446c6021100000002272bcc39000000000000000000

1 output(s) for total of 2.483446421000 dcy

stealth address amount amount idx
00: b4fc7ed257c59924a7db560ad0a206e00a0236b94a0f835d327f65a424e679d8 2.483446421000 1167110 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": 722209, "vin": [ { "gen": { "height": 722199 } } ], "vout": [ { "amount": 2483446421, "target": { "key": "b4fc7ed257c59924a7db560ad0a206e00a0236b94a0f835d327f65a424e679d8" } } ], "extra": [ 1, 26, 35, 235, 37, 19, 155, 46, 87, 83, 116, 203, 104, 253, 132, 103, 101, 145, 106, 236, 20, 246, 3, 91, 202, 208, 154, 64, 119, 212, 84, 70, 198, 2, 17, 0, 0, 0, 2, 39, 43, 204, 57, 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