Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c5a5fbee08bde8d2a0fa13530afe38f5b84daa27cc7acd1131ff6de011d6337a

Tx prefix hash: 50f9f9a41376f89f2c9c441dd8721dab6055f01e86b5dca664ce9ce14cb612f6
Tx public key: 65450dcd734fc12ff3791c09f55c8f56b5bca978c5c198acc1ca874d4ca0ad3f
Timestamp: 1743051596 Timestamp [UTC]: 2025-03-27 04:59:56 Age [y:d:h:m:s]: 01:236:19:36:09
Block: 1248164 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 433344 RingCT/type: yes/0
Extra: 0165450dcd734fc12ff3791c09f55c8f56b5bca978c5c198acc1ca874d4ca0ad3f02110000000201491f88000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 7804dc90b4ae5de093bd0f85ae9c0370bf1d7fd62f2c127106984a878b595645 0.000600000000 1735193 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": 1248174, "vin": [ { "gen": { "height": 1248164 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7804dc90b4ae5de093bd0f85ae9c0370bf1d7fd62f2c127106984a878b595645" } } ], "extra": [ 1, 101, 69, 13, 205, 115, 79, 193, 47, 243, 121, 28, 9, 245, 92, 143, 86, 181, 188, 169, 120, 197, 193, 152, 172, 193, 202, 135, 77, 76, 160, 173, 63, 2, 17, 0, 0, 0, 2, 1, 73, 31, 136, 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: