Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e95128a99ee70457cac821ef4fa8d3606f695d84cb3e5d780fa8131aafc2dca7

Tx prefix hash: c29d9b2a50a82448e9064f36141d1ae64c73610eafdc541e2e8f2aaee3d0db85
Tx public key: bdb2944583a7ac8e62f1473fee2440609cab1ee98fce47cc8c1b9f4853a0d0fc
Timestamp: 1696772788 Timestamp [UCT]: 2023-10-08 13:46:28 Age [y:d:h:m:s]: 01:172:18:31:32
Block: 865203 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 384502 RingCT/type: yes/0
Extra: 01bdb2944583a7ac8e62f1473fee2440609cab1ee98fce47cc8c1b9f4853a0d0fc021100000002bfa22221000000000000000000

1 output(s) for total of 0.834110009000 dcy

stealth address amount amount idx
00: 52051630e5e4d55f6b4fc712f9d6fb2aacff7535b237a95227836f8b37b14fd9 0.834110009000 1319729 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": 865213, "vin": [ { "gen": { "height": 865203 } } ], "vout": [ { "amount": 834110009, "target": { "key": "52051630e5e4d55f6b4fc712f9d6fb2aacff7535b237a95227836f8b37b14fd9" } } ], "extra": [ 1, 189, 178, 148, 69, 131, 167, 172, 142, 98, 241, 71, 63, 238, 36, 64, 96, 156, 171, 30, 233, 143, 206, 71, 204, 140, 27, 159, 72, 83, 160, 208, 252, 2, 17, 0, 0, 0, 2, 191, 162, 34, 33, 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