Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bf93dc44c90f26180545a8a4df4374cd96e965fe66ecc0a29853568277c3f0dd

Tx prefix hash: 1740a9aa6e6ad7bd9c24f9e02fc0e74694f6691e1e052b7740c77ea09590c13c
Tx public key: f0d8f5b874edf46fbc1dcc826e93642d3bf806aa43ac16eab774297f45a7251d
Timestamp: 1763617202 Timestamp [UTC]: 2025-11-20 05:40:02 Age [y:d:h:m:s]: 01:000:19:21:40
Block: 1416037 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 267023 RingCT/type: yes/0
Extra: 01f0d8f5b874edf46fbc1dcc826e93642d3bf806aa43ac16eab774297f45a7251d02110000000434af31cc000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: e90d5cb3a3a4e0deb8780993246e08be11cccd7a32bd1ff0b9921b06b9349a7c 0.000600000000 1904556 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": 1416047, "vin": [ { "gen": { "height": 1416037 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e90d5cb3a3a4e0deb8780993246e08be11cccd7a32bd1ff0b9921b06b9349a7c" } } ], "extra": [ 1, 240, 216, 245, 184, 116, 237, 244, 111, 188, 29, 204, 130, 110, 147, 100, 45, 59, 248, 6, 170, 67, 172, 22, 234, 183, 116, 41, 127, 69, 167, 37, 29, 2, 17, 0, 0, 0, 4, 52, 175, 49, 204, 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: