Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8f8595bfc4f3dfd3276b4fd66235e1e0cdb418630ed3e3df24398349ffa7eacb

Tx prefix hash: 89ceb8195c700fabb962bb5ca10aed299f86e33d67a552a32b13afad24178608
Tx public key: 70d54d389e9bc54c1ca941103033dd8974745017dc1a64b35de29247864d4925
Timestamp: 1774960659 Timestamp [UTC]: 2026-03-31 12:37:39 Age [y:d:h:m:s]: 00:226:21:36:16
Block: 1509798 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 167521 RingCT/type: yes/0
Extra: 0170d54d389e9bc54c1ca941103033dd8974745017dc1a64b35de29247864d4925021100000002e3d7dc9f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 4adf0c8bb094a9c15d0f69a6b9c1ddafc4d3ff0e863faa769c906141f5cd451b 0.000600000000 1999574 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": 1509808, "vin": [ { "gen": { "height": 1509798 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4adf0c8bb094a9c15d0f69a6b9c1ddafc4d3ff0e863faa769c906141f5cd451b" } } ], "extra": [ 1, 112, 213, 77, 56, 158, 155, 197, 76, 28, 169, 65, 16, 48, 51, 221, 137, 116, 116, 80, 23, 220, 26, 100, 179, 93, 226, 146, 71, 134, 77, 73, 37, 2, 17, 0, 0, 0, 2, 227, 215, 220, 159, 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: