Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ead59f4fe96fb481acbe9799c2f7425d2bf00a504fffb249b81f279ea32de36c

Tx prefix hash: b91b426680505ce3ba16afaf0889c33b4d7d37dd97beac8e5911150b26467cc1
Tx public key: 1b5e7fcf1a256d76c1495858df1be2ecd70adb71491390756d4fd7d0cf6aceb5
Timestamp: 1705230520 Timestamp [UCT]: 2024-01-14 11:08:40 Age [y:d:h:m:s]: 01:016:18:12:10
Block: 935103 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 273032 RingCT/type: yes/0
Extra: 011b5e7fcf1a256d76c1495858df1be2ecd70adb71491390756d4fd7d0cf6aceb502110000000859dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 41a74692a6a963c7d9a274a1124d41c92c4dd761820059d353c02ce05b72567b 0.600000000000 1393119 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": 935113, "vin": [ { "gen": { "height": 935103 } } ], "vout": [ { "amount": 600000000, "target": { "key": "41a74692a6a963c7d9a274a1124d41c92c4dd761820059d353c02ce05b72567b" } } ], "extra": [ 1, 27, 94, 127, 207, 26, 37, 109, 118, 193, 73, 88, 88, 223, 27, 226, 236, 215, 10, 219, 113, 73, 19, 144, 117, 109, 79, 215, 208, 207, 106, 206, 181, 2, 17, 0, 0, 0, 8, 89, 218, 211, 245, 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