Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e9ba8557a1da1f94bf30e05a0f8ca8910a00c68dbfe74f1757cff9978fd96c30

Tx prefix hash: 8a14a40ed65930c0ce868360c6d7a7e6b9a4cba9a91c00cfa8f548c176beadf9
Tx public key: 24085d5652aa696d6db85053d2eb08dcefe5ad3dad712ae3e97288923794003d
Timestamp: 1711618737 Timestamp [UCT]: 2024-03-28 09:38:57 Age [y:d:h:m:s]: 00:288:09:14:49
Block: 988084 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 206416 RingCT/type: yes/0
Extra: 0124085d5652aa696d6db85053d2eb08dcefe5ad3dad712ae3e97288923794003d02110000000a0011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 91d1a84c8b41b2f852c2f3e9f639528f11625b8b0b2723872baa4ed27d253ce9 0.600000000000 1448345 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": 988094, "vin": [ { "gen": { "height": 988084 } } ], "vout": [ { "amount": 600000000, "target": { "key": "91d1a84c8b41b2f852c2f3e9f639528f11625b8b0b2723872baa4ed27d253ce9" } } ], "extra": [ 1, 36, 8, 93, 86, 82, 170, 105, 109, 109, 184, 80, 83, 210, 235, 8, 220, 239, 229, 173, 61, 173, 113, 42, 227, 233, 114, 136, 146, 55, 148, 0, 61, 2, 17, 0, 0, 0, 10, 0, 17, 5, 91, 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