Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d6b978a1e22c3960d5a5fffd9b4f91e620470ce8050bd218a01f71c77114e85a

Tx prefix hash: 2c76778dc8fd4beb649872148ab301fe6043f4e861fd3b86425b7c137a192a05
Tx public key: e9a849651f376ca8f1ed695b506028ed5c0b0b09a9baf36617874602ed8d5dd8
Timestamp: 1718749353 Timestamp [UCT]: 2024-06-18 22:22:33 Age [y:d:h:m:s]: 00:283:01:33:39
Block: 1047187 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 202269 RingCT/type: yes/0
Extra: 01e9a849651f376ca8f1ed695b506028ed5c0b0b09a9baf36617874602ed8d5dd802110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5047560f78af8686af6ca4e2c0472e679abc6e91f83ceba6e8b0edfe54649804 0.600000000000 1517006 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": 1047197, "vin": [ { "gen": { "height": 1047187 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5047560f78af8686af6ca4e2c0472e679abc6e91f83ceba6e8b0edfe54649804" } } ], "extra": [ 1, 233, 168, 73, 101, 31, 55, 108, 168, 241, 237, 105, 91, 80, 96, 40, 237, 92, 11, 11, 9, 169, 186, 243, 102, 23, 135, 70, 2, 237, 141, 93, 216, 2, 17, 0, 0, 0, 3, 89, 218, 211, 245, 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