Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e8e58ca268c082f3e9763c679a27714372e6d5c3e20b5e635708bec6fcc78aab

Tx prefix hash: 792168eea61026459e515f1c3ddbb88455e97eb4f6eafbb08aae6eb25cbb0ccf
Tx public key: d17c26b866cb5995822683ba45f549e789e57479f0af90d68b7566db14d3086a
Timestamp: 1736496678 Timestamp [UCT]: 2025-01-10 08:11:18 Age [y:d:h:m:s]: 00:302:13:18:27
Block: 1194171 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 213744 RingCT/type: yes/0
Extra: 01d17c26b866cb5995822683ba45f549e789e57479f0af90d68b7566db14d3086a0211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1a0357e7ee5bb9a0fc6ce8e5bc0a7f8f9885623e24ba425e1ab5d0d5c41a624a 0.600000000000 1680738 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": 1194181, "vin": [ { "gen": { "height": 1194171 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1a0357e7ee5bb9a0fc6ce8e5bc0a7f8f9885623e24ba425e1ab5d0d5c41a624a" } } ], "extra": [ 1, 209, 124, 38, 184, 102, 203, 89, 149, 130, 38, 131, 186, 69, 245, 73, 231, 137, 229, 116, 121, 240, 175, 144, 214, 139, 117, 102, 219, 20, 211, 8, 106, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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