Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e6825aaf793c6885ca0b7301819f921c776a1841565d88b1c9d42c1b38e00a4f

Tx prefix hash: aa4642329787113a5fd2ae1c3f5e4a8ded71d9d00c36886ff9c823b804b69e11
Tx public key: 4fd35f049ef6e6423556885272e481da389374c9dee54a0c0c2bb054fda71125
Timestamp: 1722597740 Timestamp [UCT]: 2024-08-02 11:22:20 Age [y:d:h:m:s]: 00:083:10:05:00
Block: 1079093 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 59716 RingCT/type: yes/0
Extra: 014fd35f049ef6e6423556885272e481da389374c9dee54a0c0c2bb054fda7112502110000000991e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 56f518612a75cc55a9ee843c5965aeaf010bf4f28404e5abb92b81d7174dc367 0.600000000000 1551898 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": 1079103, "vin": [ { "gen": { "height": 1079093 } } ], "vout": [ { "amount": 600000000, "target": { "key": "56f518612a75cc55a9ee843c5965aeaf010bf4f28404e5abb92b81d7174dc367" } } ], "extra": [ 1, 79, 211, 95, 4, 158, 246, 230, 66, 53, 86, 136, 82, 114, 228, 129, 218, 56, 147, 116, 201, 222, 229, 74, 12, 12, 43, 176, 84, 253, 167, 17, 37, 2, 17, 0, 0, 0, 9, 145, 225, 60, 4, 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