Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 09d2dff9556e44a68069a0a66a04bcb86304e6f3020e9d2f1a9cc85339c47608

Tx prefix hash: 18c196c90a092ce040018dbe910d1bd80c0c383b6a404bc80138f4b9425e4043
Tx public key: 6df866dbda15da7592bfdeb37dbebb1f9eb9106943f932d914bdebdba540a6e4
Timestamp: 1698034190 Timestamp [UCT]: 2023-10-23 04:09:50 Age [y:d:h:m:s]: 01:171:06:45:44
Block: 875649 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 383442 RingCT/type: yes/0
Extra: 016df866dbda15da7592bfdeb37dbebb1f9eb9106943f932d914bdebdba540a6e40211000000024b8f5122000000000000000000

1 output(s) for total of 0.770213955000 dcy

stealth address amount amount idx
00: 5bf851e942963d081b5ab5419c1c337a2022e0c9bb0c983c54411feb8c1e56e3 0.770213955000 1330913 of 0

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": 875659, "vin": [ { "gen": { "height": 875649 } } ], "vout": [ { "amount": 770213955, "target": { "key": "5bf851e942963d081b5ab5419c1c337a2022e0c9bb0c983c54411feb8c1e56e3" } } ], "extra": [ 1, 109, 248, 102, 219, 218, 21, 218, 117, 146, 191, 222, 179, 125, 190, 187, 31, 158, 185, 16, 105, 67, 249, 50, 217, 20, 189, 235, 219, 165, 64, 166, 228, 2, 17, 0, 0, 0, 2, 75, 143, 81, 34, 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