Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: df9a08c3152e69ed5ed3f8c9938eaf5500437d0f640c7ffe9958417a6926d580

Tx prefix hash: 66a350c9cffa5874aab6e3fe93e5d2071fe9829c4ecbf8a1f7a2d2399eea497f
Tx public key: 27da1b8580772c5c5175b2c5b7b627ae73ba412802a8f52035171b636a2ed159
Timestamp: 1709133606 Timestamp [UCT]: 2024-02-28 15:20:06 Age [y:d:h:m:s]: 01:280:02:28:01
Block: 967476 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 458958 RingCT/type: yes/0
Extra: 0127da1b8580772c5c5175b2c5b7b627ae73ba412802a8f52035171b636a2ed15902110000000759dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 16fd3c394b757cbcbb07cafc4d2ccf9c0c7ed89772ff42c072dd8302ac3e9eb9 0.600000000000 1427255 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": 967486, "vin": [ { "gen": { "height": 967476 } } ], "vout": [ { "amount": 600000000, "target": { "key": "16fd3c394b757cbcbb07cafc4d2ccf9c0c7ed89772ff42c072dd8302ac3e9eb9" } } ], "extra": [ 1, 39, 218, 27, 133, 128, 119, 44, 92, 81, 117, 178, 197, 183, 182, 39, 174, 115, 186, 65, 40, 2, 168, 245, 32, 53, 23, 27, 99, 106, 46, 209, 89, 2, 17, 0, 0, 0, 7, 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