Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d631789b00054efadb59064d2bbcfcc22cd17527779621bd67c3186bcd418dbd

Tx prefix hash: 4733881f42c30603001e8d1f0bcb8f0597c36b45526dd7951b2725dc5df66c77
Tx public key: 757f18376b16d9c6b5de49cf4ee7c9e3c24b5c1189a2bda9d9bfaa043792dc9e
Timestamp: 1698872821 Timestamp [UCT]: 2023-11-01 21:07:01 Age [y:d:h:m:s]: 01:145:13:16:44
Block: 882603 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 365008 RingCT/type: yes/0
Extra: 01757f18376b16d9c6b5de49cf4ee7c9e3c24b5c1189a2bda9d9bfaa043792dc9e021100000004e6d27f9c000000000000000000

1 output(s) for total of 0.730415337000 dcy

stealth address amount amount idx
00: b9c5c82b5df975a70dac3e6c3c34fe33ad8be520e47e5c9379decd08bdc03295 0.730415337000 1338273 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": 882613, "vin": [ { "gen": { "height": 882603 } } ], "vout": [ { "amount": 730415337, "target": { "key": "b9c5c82b5df975a70dac3e6c3c34fe33ad8be520e47e5c9379decd08bdc03295" } } ], "extra": [ 1, 117, 127, 24, 55, 107, 22, 217, 198, 181, 222, 73, 207, 78, 231, 201, 227, 194, 75, 92, 17, 137, 162, 189, 169, 217, 191, 170, 4, 55, 146, 220, 158, 2, 17, 0, 0, 0, 4, 230, 210, 127, 156, 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