Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c3426f12347dfb9f2eb18af090b01b9ea470a4cdc8e66b936a6ca8fd289ca1c5

Tx prefix hash: 41d1d8ab0de291112b337c6ca6677c8366b34e25281a648af8902167f12fcaf8
Tx public key: 20e92455d984abc8d825d48e5a8d765e8acb20d96ad35a69346a133512f851e0
Timestamp: 1706295346 Timestamp [UCT]: 2024-01-26 18:55:46 Age [y:d:h:m:s]: 01:030:09:22:25
Block: 943906 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 282779 RingCT/type: yes/0
Extra: 0120e92455d984abc8d825d48e5a8d765e8acb20d96ad35a69346a133512f851e002110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6d10aa724e1c1161603a02a4e0269cd3e9a01d972e3c99524def009c2fcbd987 0.600000000000 1402132 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": 943916, "vin": [ { "gen": { "height": 943906 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6d10aa724e1c1161603a02a4e0269cd3e9a01d972e3c99524def009c2fcbd987" } } ], "extra": [ 1, 32, 233, 36, 85, 217, 132, 171, 200, 216, 37, 212, 142, 90, 141, 118, 94, 138, 203, 32, 217, 106, 211, 90, 105, 52, 106, 19, 53, 18, 248, 81, 224, 2, 17, 0, 0, 0, 3, 82, 212, 126, 148, 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