Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f32a112d759dffb3935b42bb80bd64dc0a6a2fc6bcc62ba9e62d038f0c88cf15

Tx prefix hash: 601394acf0600a985e0fad64e93cf7fe331aae35224ec758836e1fba325afded
Tx public key: 4ac45caf3b3d4a45e2c87fe5efb28044e759619bdea1947d9fe75ff20a8ba3d1
Timestamp: 1707837676 Timestamp [UCT]: 2024-02-13 15:21:16 Age [y:d:h:m:s]: 01:054:18:33:49
Block: 956720 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 300175 RingCT/type: yes/0
Extra: 014ac45caf3b3d4a45e2c87fe5efb28044e759619bdea1947d9fe75ff20a8ba3d10211000000057a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9dba00c8841fce5cb13113440b02549805a3349e784147627e6f628d11d12ef0 0.600000000000 1416030 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": 956730, "vin": [ { "gen": { "height": 956720 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9dba00c8841fce5cb13113440b02549805a3349e784147627e6f628d11d12ef0" } } ], "extra": [ 1, 74, 196, 92, 175, 59, 61, 74, 69, 226, 200, 127, 229, 239, 178, 128, 68, 231, 89, 97, 155, 222, 161, 148, 125, 159, 231, 95, 242, 10, 139, 163, 209, 2, 17, 0, 0, 0, 5, 122, 156, 244, 199, 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