Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b4daee8577737684835a3b051ac2ab4b5ebec5ab6c94f7bad7f7ba0c8f7af58a

Tx prefix hash: 3e2eeffc84e844584bbff95523270667ae59e9012b2b05e281638ab0d535578d
Tx public key: b5c8f3819cc2676fac19253a17191b1d7aa0a3316ad407480b434d5b992f72bf
Timestamp: 1715846398 Timestamp [UCT]: 2024-05-16 07:59:58 Age [y:d:h:m:s]: 00:237:23:25:14
Block: 1023129 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 170314 RingCT/type: yes/0
Extra: 01b5c8f3819cc2676fac19253a17191b1d7aa0a3316ad407480b434d5b992f72bf02110000000179bda3be000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1685f9ee95a7d9961e8e0f8049e947d3bb2688fdb3e401cdc9eced0d494a4820 0.600000000000 1487928 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": 1023139, "vin": [ { "gen": { "height": 1023129 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1685f9ee95a7d9961e8e0f8049e947d3bb2688fdb3e401cdc9eced0d494a4820" } } ], "extra": [ 1, 181, 200, 243, 129, 156, 194, 103, 111, 172, 25, 37, 58, 23, 25, 27, 29, 122, 160, 163, 49, 106, 212, 7, 72, 11, 67, 77, 91, 153, 47, 114, 191, 2, 17, 0, 0, 0, 1, 121, 189, 163, 190, 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