Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 936baf5e0769bb2d8b88fff1a8092acdbf0dfaf9211e1c150a6c0544b0be050f

Tx prefix hash: eea829dd0238312ac5018d70d0a702a97308193c6ec3b787d4b6bd814f0a85e0
Tx public key: fac4e4ea5be61353a50103e2cc33d4fb7eded3de58394c82841a609a910edccb
Timestamp: 1726529278 Timestamp [UCT]: 2024-09-16 23:27:58 Age [y:d:h:m:s]: 00:159:11:58:27
Block: 1111676 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 113789 RingCT/type: yes/0
Extra: 01fac4e4ea5be61353a50103e2cc33d4fb7eded3de58394c82841a609a910edccb02110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e7d2b4b7433da97af5ad0da1e1990986ec0f5b9b10011d1a416263a91d9ca40b 0.600000000000 1590725 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": 1111686, "vin": [ { "gen": { "height": 1111676 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e7d2b4b7433da97af5ad0da1e1990986ec0f5b9b10011d1a416263a91d9ca40b" } } ], "extra": [ 1, 250, 196, 228, 234, 91, 230, 19, 83, 165, 1, 3, 226, 204, 51, 212, 251, 126, 222, 211, 222, 88, 57, 76, 130, 132, 26, 96, 154, 145, 14, 220, 203, 2, 17, 0, 0, 0, 4, 145, 225, 60, 4, 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