Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0e3e7626c7eff64e3258beca47654f2158dbef9fdb711706975bb492952592b6

Tx prefix hash: 41e8a1bc0a6ed3ddbc058a9b233eaaade5208a739c09eb6d1aea784503d8cc18
Tx public key: e10ab0b3d9e3ec62324a3bfc6454aee229f3d334e88d60ac0532185a9bf7af0c
Timestamp: 1698437054 Timestamp [UCT]: 2023-10-27 20:04:14 Age [y:d:h:m:s]: 01:221:19:11:30
Block: 878999 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 419578 RingCT/type: yes/0
Extra: 01e10ab0b3d9e3ec62324a3bfc6454aee229f3d334e88d60ac0532185a9bf7af0c021100000009e6d27f9c000000000000000000

1 output(s) for total of 0.750777826000 dcy

stealth address amount amount idx
00: 3d0e3de5007cb9b4db1d000f2c8f1dcdff3744a94b674d98b648cd55e3c0eb93 0.750777826000 1334495 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": 879009, "vin": [ { "gen": { "height": 878999 } } ], "vout": [ { "amount": 750777826, "target": { "key": "3d0e3de5007cb9b4db1d000f2c8f1dcdff3744a94b674d98b648cd55e3c0eb93" } } ], "extra": [ 1, 225, 10, 176, 179, 217, 227, 236, 98, 50, 74, 59, 252, 100, 84, 174, 226, 41, 243, 211, 52, 232, 141, 96, 172, 5, 50, 24, 90, 155, 247, 175, 12, 2, 17, 0, 0, 0, 9, 230, 210, 127, 156, 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