Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cfbafe24dbef0b22f17097989024ab4d42a2000cd279d872f57304b94b66524b

Tx prefix hash: d8d1a17b058ca972946e09e643288fb759b8578c3ca8a48813161e191954d9bd
Tx public key: 4116c1b4d4a9557f74c9af6a66fa7a3295c0c61e2952a157d268d3e951a113e1
Timestamp: 1735089367 Timestamp [UCT]: 2024-12-25 01:16:07 Age [y:d:h:m:s]: 00:091:10:14:47
Block: 1182542 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 65096 RingCT/type: yes/0
Extra: 014116c1b4d4a9557f74c9af6a66fa7a3295c0c61e2952a157d268d3e951a113e10211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 95986beedd2407e8f0ec84f4e9af6b52154b4fb9d36bb844fb05e7acfdc37117 0.600000000000 1668977 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": 1182552, "vin": [ { "gen": { "height": 1182542 } } ], "vout": [ { "amount": 600000000, "target": { "key": "95986beedd2407e8f0ec84f4e9af6b52154b4fb9d36bb844fb05e7acfdc37117" } } ], "extra": [ 1, 65, 22, 193, 180, 212, 169, 85, 127, 116, 201, 175, 106, 102, 250, 122, 50, 149, 192, 198, 30, 41, 82, 161, 87, 210, 104, 211, 233, 81, 161, 19, 225, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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