Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0e4e74a466ef0fa2d9b85a7f464c98c63f72a1c08f3b72c766df5ea6df318de0

Tx prefix hash: 799dcf02aac652a87fd668004da47c9c506ca9ee94c070601a5e209871f5e96c
Tx public key: 018bb589e56f6e330eb32f440350edfbcc615936851b5dd2ee034c4fc57346b0
Timestamp: 1660623699 Timestamp [UCT]: 2022-08-16 04:21:39 Age [y:d:h:m:s]: 03:130:10:21:36
Block: 566850 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 873073 RingCT/type: yes/0
Extra: 01018bb589e56f6e330eb32f440350edfbcc615936851b5dd2ee034c4fc57346b00211000000046570b1ef000000000000000000

1 output(s) for total of 8.124389701000 dcy

stealth address amount amount idx
00: d6fad86fd7d395245e796aa6d1e5d727eafa19ae87e87599303c0efe5eb7a670 8.124389701000 999887 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": 566860, "vin": [ { "gen": { "height": 566850 } } ], "vout": [ { "amount": 8124389701, "target": { "key": "d6fad86fd7d395245e796aa6d1e5d727eafa19ae87e87599303c0efe5eb7a670" } } ], "extra": [ 1, 1, 139, 181, 137, 229, 111, 110, 51, 14, 179, 47, 68, 3, 80, 237, 251, 204, 97, 89, 54, 133, 27, 93, 210, 238, 3, 76, 79, 197, 115, 70, 176, 2, 17, 0, 0, 0, 4, 101, 112, 177, 239, 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