Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d9db32b707e3f027fc6f31e54078282bacbf51458d187a938174a43ca9de56a1

Tx prefix hash: fb904ce328425abff21536bdcd3dda6b8561e0f421fccd7821308c847a4323a6
Tx public key: 29d17017dc019adff3c1d06e95d1a43a5a42099c24f53b5700e72158e412a373
Timestamp: 1707346155 Timestamp [UCT]: 2024-02-07 22:49:15 Age [y:d:h:m:s]: 01:059:16:26:25
Block: 952648 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 303702 RingCT/type: yes/0
Extra: 0129d17017dc019adff3c1d06e95d1a43a5a42099c24f53b5700e72158e412a37302110000000110a1748f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 687a9b8ffc03041dc3a601061f8843f3a1c642f87e8ccfb37ff02edc2f3d7217 0.600000000000 1411738 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": 952658, "vin": [ { "gen": { "height": 952648 } } ], "vout": [ { "amount": 600000000, "target": { "key": "687a9b8ffc03041dc3a601061f8843f3a1c642f87e8ccfb37ff02edc2f3d7217" } } ], "extra": [ 1, 41, 209, 112, 23, 220, 1, 154, 223, 243, 193, 208, 110, 149, 209, 164, 58, 90, 66, 9, 156, 36, 245, 59, 87, 0, 231, 33, 88, 228, 18, 163, 115, 2, 17, 0, 0, 0, 1, 16, 161, 116, 143, 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