Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 51f420a04f3b686d60f04ca6e5f92e6b0d49b6c93efbd44764651d312f9b5a89

Tx prefix hash: 4e9393d50ce57278639d7e8d4bc25f8a3501c5f43bd1dbb25ff818b6656e7481
Tx public key: 79178807b1facb9f62072e51e9871bc19e026d591e9601f4a84cca2d0ff3f5e4
Timestamp: 1746798920 Timestamp [UCT]: 2025-05-09 13:55:20 Age [y:d:h:m:s]: 00:151:14:57:59
Block: 1279196 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 106019 RingCT/type: yes/0
Extra: 0179178807b1facb9f62072e51e9871bc19e026d591e9601f4a84cca2d0ff3f5e402110000000a1f90517a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ea1763153296624a96a783a52131433813bedb47b5ef444003d97a29c9ec8d18 0.600000000000 1766569 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": 1279206, "vin": [ { "gen": { "height": 1279196 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ea1763153296624a96a783a52131433813bedb47b5ef444003d97a29c9ec8d18" } } ], "extra": [ 1, 121, 23, 136, 7, 177, 250, 203, 159, 98, 7, 46, 81, 233, 135, 27, 193, 158, 2, 109, 89, 30, 150, 1, 244, 168, 76, 202, 45, 15, 243, 245, 228, 2, 17, 0, 0, 0, 10, 31, 144, 81, 122, 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