Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9e5b6fdce609851091d76e79a87313342cd22202502f797ffec419e7e55aaf70

Tx prefix hash: c8261c9bea8bc60c0440e2af5045753c0d661a131bf024ef532b45db3854ef86
Tx public key: 585a4c3eddd0ba6cdee984b6a25c081cd7749c9bf916024d4f4e19dbef9664a4
Timestamp: 1694867058 Timestamp [UCT]: 2023-09-16 12:24:18 Age [y:d:h:m:s]: 01:276:11:25:44
Block: 849381 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 458595 RingCT/type: yes/0
Extra: 01585a4c3eddd0ba6cdee984b6a25c081cd7749c9bf916024d4f4e19dbef9664a4021100000004e6d27f9c000000000000000000

1 output(s) for total of 0.941156949000 dcy

stealth address amount amount idx
00: 801b45cbdf10e1be8bfd71fb98f6e4c9aecfac22c23165f0ebc7f7e266f95969 0.941156949000 1303041 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": 849391, "vin": [ { "gen": { "height": 849381 } } ], "vout": [ { "amount": 941156949, "target": { "key": "801b45cbdf10e1be8bfd71fb98f6e4c9aecfac22c23165f0ebc7f7e266f95969" } } ], "extra": [ 1, 88, 90, 76, 62, 221, 208, 186, 108, 222, 233, 132, 182, 162, 92, 8, 28, 215, 116, 156, 155, 249, 22, 2, 77, 79, 78, 25, 219, 239, 150, 100, 164, 2, 17, 0, 0, 0, 4, 230, 210, 127, 156, 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