Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2e0fff7f8fab7f10633211539467bfdd3bc0331b36ef56ab1ed5a3d49198861f

Tx prefix hash: 83b7fc6c3d9e86250a5f20f8f5e34c5d35f43bdc440284736246797fedd9e7aa
Tx public key: 4f69e0af47241e312c3815c92b7025dc62dbc954d0bb01d27ac6fc96833125d8
Timestamp: 1732865276 Timestamp [UCT]: 2024-11-29 07:27:56 Age [y:d:h:m:s]: 00:131:21:02:08
Block: 1164120 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 94056 RingCT/type: yes/0
Extra: 014f69e0af47241e312c3815c92b7025dc62dbc954d0bb01d27ac6fc96833125d80211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d0e5bf469609cb75df89a2c711fc560368dd0e85a1283232e908e1e88a60fc24 0.600000000000 1649793 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": 1164130, "vin": [ { "gen": { "height": 1164120 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d0e5bf469609cb75df89a2c711fc560368dd0e85a1283232e908e1e88a60fc24" } } ], "extra": [ 1, 79, 105, 224, 175, 71, 36, 30, 49, 44, 56, 21, 201, 43, 112, 37, 220, 98, 219, 201, 84, 208, 187, 1, 210, 122, 198, 252, 150, 131, 49, 37, 216, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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