Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 878a44cb5c7829e0a97589edde694eaea57b1e1cdcc0f9eb65f42faf5cce0d47

Tx prefix hash: 298935ceb15bafc904a7040fb27b89ba91f1c77b5d8965e6d84bbca37e01f515
Tx public key: 3c7bed5298c23c786ecaeaed89e44f18df6d7168e9b25b3cb31f3f23ba2af0fb
Timestamp: 1747564204 Timestamp [UTC]: 2025-05-18 10:30:04 Age [y:d:h:m:s]: 01:187:20:45:13
Block: 1285537 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 397957 RingCT/type: yes/0
Extra: 013c7bed5298c23c786ecaeaed89e44f18df6d7168e9b25b3cb31f3f23ba2af0fb0211000000079f9fe68c000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: e740ee5eb1c480979e0b3549a864406038018f849d0330905de911709af9e41f 0.000600000000 1773002 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": 1285547, "vin": [ { "gen": { "height": 1285537 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e740ee5eb1c480979e0b3549a864406038018f849d0330905de911709af9e41f" } } ], "extra": [ 1, 60, 123, 237, 82, 152, 194, 60, 120, 110, 202, 234, 237, 137, 228, 79, 24, 223, 109, 113, 104, 233, 178, 91, 60, 179, 31, 63, 35, 186, 42, 240, 251, 2, 17, 0, 0, 0, 7, 159, 159, 230, 140, 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: