Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2d8231ca99cdc0294f81577139447321cd9d562accae5efcda11fd9b9241ff20

Tx prefix hash: 358d6a9319a027a53dd315e7e7396e6f80d8eb24f68d0098d5b218681b5c9165
Tx public key: 967b4c34c9797d819f9819a0ff263522d6ab79c86a3e50a0f568c3a96a39fce7
Timestamp: 1727735735 Timestamp [UCT]: 2024-09-30 22:35:35 Age [y:d:h:m:s]: 00:114:05:32:54
Block: 1121690 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 81626 RingCT/type: yes/0
Extra: 01967b4c34c9797d819f9819a0ff263522d6ab79c86a3e50a0f568c3a96a39fce7021100000006e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0b09e070669cc2a7395dc382e40ed0fe20166696c1191ef24e3ace8243460f90 0.600000000000 1604007 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": 1121700, "vin": [ { "gen": { "height": 1121690 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0b09e070669cc2a7395dc382e40ed0fe20166696c1191ef24e3ace8243460f90" } } ], "extra": [ 1, 150, 123, 76, 52, 201, 121, 125, 129, 159, 152, 25, 160, 255, 38, 53, 34, 214, 171, 121, 200, 106, 62, 80, 160, 245, 104, 195, 169, 106, 57, 252, 231, 2, 17, 0, 0, 0, 6, 233, 20, 221, 21, 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