Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8105f0a4f4ed1b1d289005b64250cb54a974026b0f38e686e35288f6efa9f90e

Tx prefix hash: 2715cd374504146f1d78bf9587c7a197bd93968cb454e614946f61f0b4233dd9
Tx public key: 5c00718b20db7e044a2170a34e770d0be5ca06ea37c5ba44bd0f69e64df2eb85
Timestamp: 1707691890 Timestamp [UCT]: 2024-02-11 22:51:30 Age [y:d:h:m:s]: 01:087:05:26:39
Block: 955507 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 323399 RingCT/type: yes/0
Extra: 015c00718b20db7e044a2170a34e770d0be5ca06ea37c5ba44bd0f69e64df2eb850211000000060011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b85b9ec87c0efbb5c821392ca7d1ed84bb9a69834ba72f6f30c897cf2aeeda48 0.600000000000 1414799 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": 955517, "vin": [ { "gen": { "height": 955507 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b85b9ec87c0efbb5c821392ca7d1ed84bb9a69834ba72f6f30c897cf2aeeda48" } } ], "extra": [ 1, 92, 0, 113, 139, 32, 219, 126, 4, 74, 33, 112, 163, 78, 119, 13, 11, 229, 202, 6, 234, 55, 197, 186, 68, 189, 15, 105, 230, 77, 242, 235, 133, 2, 17, 0, 0, 0, 6, 0, 17, 5, 91, 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