Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1b6cff4b27ac6bf53f32afd49fa96a92af38f984389f7ab91f87ef727a022d12

Tx prefix hash: 16b140d1b5e74669724f951a9655f4a09a5855d0bb3e308091ad933ba0e771b0
Tx public key: dc2f8bc983db5b596763b38b6b17cd0ee6122ee241f6fa258b5d5f15297ced81
Timestamp: 1702462000 Timestamp [UCT]: 2023-12-13 10:06:40 Age [y:d:h:m:s]: 01:154:06:14:52
Block: 912180 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 371387 RingCT/type: yes/0
Extra: 01dc2f8bc983db5b596763b38b6b17cd0ee6122ee241f6fa258b5d5f15297ced8102110000000733af99f4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7ca866e532d2a6acbfc354121a15de76da388020ac9bb3da67b773b8cb0c26a4 0.600000000000 1369402 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": 912190, "vin": [ { "gen": { "height": 912180 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7ca866e532d2a6acbfc354121a15de76da388020ac9bb3da67b773b8cb0c26a4" } } ], "extra": [ 1, 220, 47, 139, 201, 131, 219, 91, 89, 103, 99, 179, 139, 107, 23, 205, 14, 230, 18, 46, 226, 65, 246, 250, 37, 139, 93, 95, 21, 41, 124, 237, 129, 2, 17, 0, 0, 0, 7, 51, 175, 153, 244, 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