Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fd2ba1f50366aef48a04ca9e836e76e2cc097ed9f7fef9d619b3875dbe0392f4

Tx prefix hash: f102a7b5d5eac0040947106e81f9952ed94a16feaa5d36323ae5eb473561b5d1
Tx public key: 34ffbd1c35f186b9baa6eb9f6adb5941521091e25748e8c4a9ad719082f8c70a
Timestamp: 1712239109 Timestamp [UCT]: 2024-04-04 13:58:29 Age [y:d:h:m:s]: 01:073:16:34:49
Block: 993180 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 313587 RingCT/type: yes/0
Extra: 0134ffbd1c35f186b9baa6eb9f6adb5941521091e25748e8c4a9ad719082f8c70a02110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1b6eaacd19f26d200b6bc72a7641f9fab9b359cf83aa9ad2f1673a4b6f3f198f 0.600000000000 1453562 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": 993190, "vin": [ { "gen": { "height": 993180 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1b6eaacd19f26d200b6bc72a7641f9fab9b359cf83aa9ad2f1673a4b6f3f198f" } } ], "extra": [ 1, 52, 255, 189, 28, 53, 241, 134, 185, 186, 166, 235, 159, 106, 219, 89, 65, 82, 16, 145, 226, 87, 72, 232, 196, 169, 173, 113, 144, 130, 248, 199, 10, 2, 17, 0, 0, 0, 1, 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