Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 71ecc7ad19c9dbdae32389e6f436ba459c6ab5b4137f32db830322265095c05c

Tx prefix hash: 7d0938e583df269b3637b8af6b6e2f7341ba1427e5474ddb36ddf7873493c005
Tx public key: 1c5e8bf67d98c0c1f84e366a90ca16ceb1cbc521b14abf4174eef2f0ff234357
Timestamp: 1677817136 Timestamp [UCT]: 2023-03-03 04:18:56 Age [y:d:h:m:s]: 02:084:15:29:41
Block: 708726 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 582104 RingCT/type: yes/0
Extra: 011c5e8bf67d98c0c1f84e366a90ca16ceb1cbc521b14abf4174eef2f0ff2343570211000000015029cbac000000000000000000

1 output(s) for total of 2.752304349000 dcy

stealth address amount amount idx
00: b9058a90f18c21c9e964b8e11d6b5e5461367aab67fd29f8173cbd9dea67f732 2.752304349000 1152637 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": 708736, "vin": [ { "gen": { "height": 708726 } } ], "vout": [ { "amount": 2752304349, "target": { "key": "b9058a90f18c21c9e964b8e11d6b5e5461367aab67fd29f8173cbd9dea67f732" } } ], "extra": [ 1, 28, 94, 139, 246, 125, 152, 192, 193, 248, 78, 54, 106, 144, 202, 22, 206, 177, 203, 197, 33, 177, 74, 191, 65, 116, 238, 242, 240, 255, 35, 67, 87, 2, 17, 0, 0, 0, 1, 80, 41, 203, 172, 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