Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 13f77e71bbcda7f29d42ced1ed323b8b0ae1731afa73149d27d9a92ae4214d6b

Tx prefix hash: 77e39e34d6f35b151988caa5e6334a16abe4bb6be3cb7e8472d6b647b8577a3b
Tx public key: 991df63c29dd58485f79b1296b78c78bcf03042baead2c599983c21bd3d2e52b
Timestamp: 1705226994 Timestamp [UCT]: 2024-01-14 10:09:54 Age [y:d:h:m:s]: 01:083:01:59:50
Block: 935075 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 320465 RingCT/type: yes/0
Extra: 01991df63c29dd58485f79b1296b78c78bcf03042baead2c599983c21bd3d2e52b021100000001bfa22221000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a7b33bc1e3b051440b41e334bf8d964596915741ede8a9dfabf5ed207e8b96a7 0.600000000000 1393091 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": 935085, "vin": [ { "gen": { "height": 935075 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a7b33bc1e3b051440b41e334bf8d964596915741ede8a9dfabf5ed207e8b96a7" } } ], "extra": [ 1, 153, 29, 246, 60, 41, 221, 88, 72, 95, 121, 177, 41, 107, 120, 199, 139, 207, 3, 4, 43, 174, 173, 44, 89, 153, 131, 194, 27, 211, 210, 229, 43, 2, 17, 0, 0, 0, 1, 191, 162, 34, 33, 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