Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9f906978f62968beb3e4585488c1a1b0a89e70965dea6e06ea6484e9becbedcb

Tx prefix hash: 15db48c01ece49d0d75b7d0f8407f5729d1816dcebdda357d173af6be26f47a1
Tx public key: 100e934db40f9aa1b7baa72b40a4327a43c571855206aa16d458c7adae4d1eeb
Timestamp: 1736173952 Timestamp [UCT]: 2025-01-06 14:32:32 Age [y:d:h:m:s]: 00:162:16:41:45
Block: 1191524 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 115972 RingCT/type: yes/0
Extra: 01100e934db40f9aa1b7baa72b40a4327a43c571855206aa16d458c7adae4d1eeb021100000007007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d1db1d61dd9df99aba762f37abfd9515ac4a670ef267fd5460a0b6395121bd04 0.600000000000 1678063 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": 1191534, "vin": [ { "gen": { "height": 1191524 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d1db1d61dd9df99aba762f37abfd9515ac4a670ef267fd5460a0b6395121bd04" } } ], "extra": [ 1, 16, 14, 147, 77, 180, 15, 154, 161, 183, 186, 167, 43, 64, 164, 50, 122, 67, 197, 113, 133, 82, 6, 170, 22, 212, 88, 199, 173, 174, 77, 30, 235, 2, 17, 0, 0, 0, 7, 0, 127, 151, 138, 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