Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 338f3ecd2803b852cfa6700afa7ec3add0446cfda20898fe180493a6a30ae8e9

Tx prefix hash: 2676c4ef2e33cb0a0862b747ff5b12e27b69dbd6576aeeebd622e0e0ae1219b4
Tx public key: cb3efae45b7c5fa437ef10daadd6f46473c41ce432ff22f5f790f9d94afe03b2
Timestamp: 1720439507 Timestamp [UCT]: 2024-07-08 11:51:47 Age [y:d:h:m:s]: 00:275:15:51:07
Block: 1061209 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 196949 RingCT/type: yes/0
Extra: 01cb3efae45b7c5fa437ef10daadd6f46473c41ce432ff22f5f790f9d94afe03b2021100000011e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bc3fd3246cc899e8de3839728b4be89442ed2770310779174ae21f7b7fda3883 0.600000000000 1531700 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": 1061219, "vin": [ { "gen": { "height": 1061209 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bc3fd3246cc899e8de3839728b4be89442ed2770310779174ae21f7b7fda3883" } } ], "extra": [ 1, 203, 62, 250, 228, 91, 124, 95, 164, 55, 239, 16, 218, 173, 214, 244, 100, 115, 196, 28, 228, 50, 255, 34, 245, 247, 144, 249, 217, 74, 254, 3, 178, 2, 17, 0, 0, 0, 17, 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