Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0ac6641b1ed51053818762ac868d7d8d071bec799f4803d6d89e81d1528f51db

Tx prefix hash: 979a1c1e6386c412aaab6f4f542dca13aa2b0c5a9890c83c6b2f6e6127933f2c
Tx public key: 8130a0dcf735ce081c624430f063364954e29d731e1b2f03500f4e139a3e0635
Timestamp: 1762305383 Timestamp [UCT]: 2025-11-05 01:16:23 Age [y:d:h:m:s]: 00:047:11:25:56
Block: 1405150 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 34008 RingCT/type: yes/0
Extra: 018130a0dcf735ce081c624430f063364954e29d731e1b2f03500f4e139a3e06350211000000012609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fd5a768b81eacc9b946bd79b7a0cae75164de250b08c4ad4ec34e770944d9cc3 0.600000000000 1893521 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": 1405160, "vin": [ { "gen": { "height": 1405150 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fd5a768b81eacc9b946bd79b7a0cae75164de250b08c4ad4ec34e770944d9cc3" } } ], "extra": [ 1, 129, 48, 160, 220, 247, 53, 206, 8, 28, 98, 68, 48, 240, 99, 54, 73, 84, 226, 157, 115, 30, 27, 47, 3, 80, 15, 78, 19, 154, 62, 6, 53, 2, 17, 0, 0, 0, 1, 38, 9, 179, 160, 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