Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8197f93a2047ac1fcc2b5fe0d8d4551821bf08d9af5dc27ab5333b6dca1997c8

Tx prefix hash: 556fab7f848596e5fcbca6e817bc664d54465d3a0b78ebcbbe32c7d224bf4474
Tx public key: 10aa579f2bd14d7af707460f0ac8b489ae363cfd2f006ba70d4451af9dfaa686
Timestamp: 1742203885 Timestamp [UTC]: 2025-03-17 09:31:25 Age [y:d:h:m:s]: 01:053:09:41:27
Block: 1241179 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 289381 RingCT/type: yes/0
Extra: 0110aa579f2bd14d7af707460f0ac8b489ae363cfd2f006ba70d4451af9dfaa686021100000002007f978a000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: fe086189d3db59e56baf76a710e7161603d67d8a4a44b2635d9f5e0f900bcf72 0.000600000000 1728152 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 dinastycoin-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": 1241189, "vin": [ { "gen": { "height": 1241179 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fe086189d3db59e56baf76a710e7161603d67d8a4a44b2635d9f5e0f900bcf72" } } ], "extra": [ 1, 16, 170, 87, 159, 43, 209, 77, 122, 247, 7, 70, 15, 10, 200, 180, 137, 174, 54, 60, 253, 47, 0, 107, 167, 13, 68, 81, 175, 157, 250, 166, 134, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): devel-2026-02-02-6303d2a (1.2) | monero version: