Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9a830c838d834dc444af959c7f6a3748cbd13271bb737e6e57dbb8e94cf73adf

Tx prefix hash: 07967e9ff3ca9d2ab449a719df79eb96893d380826b715ed11b2915898f47c44
Tx public key: 6ec7a814a55aadb81bf032c28f82c1a8fa5af05620455326ab22e78109ffd6ac
Timestamp: 1705571011 Timestamp [UCT]: 2024-01-18 09:43:31 Age [y:d:h:m:s]: 01:077:21:07:55
Block: 937917 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 316754 RingCT/type: yes/0
Extra: 016ec7a814a55aadb81bf032c28f82c1a8fa5af05620455326ab22e78109ffd6ac02110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4d5ae2f79a9c5cfcb25fcb90bb5b1563d505d5272da1a76c9f92d0e2da2a5f9c 0.600000000000 1395981 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": 937927, "vin": [ { "gen": { "height": 937917 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4d5ae2f79a9c5cfcb25fcb90bb5b1563d505d5272da1a76c9f92d0e2da2a5f9c" } } ], "extra": [ 1, 110, 199, 168, 20, 165, 90, 173, 184, 27, 240, 50, 194, 143, 130, 193, 168, 250, 90, 240, 86, 32, 69, 83, 38, 171, 34, 231, 129, 9, 255, 214, 172, 2, 17, 0, 0, 0, 3, 89, 218, 211, 245, 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