Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c4c35bc6d1ead1c666f61d4fc5f88edc241028dc67f7321bc4197cffdc60acb5

Tx prefix hash: b2caddbef9d794e6507baad9d9ea5a8677888ae359d700dcc24b1666bdd90acd
Tx public key: b8af2c241c78fa9d315b1ae27406aab9faecd34b49bd81bee61e696681314f3b
Timestamp: 1747266906 Timestamp [UTC]: 2025-05-14 23:55:06 Age [y:d:h:m:s]: 00:361:09:16:09
Block: 1283083 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 248446 RingCT/type: yes/0
Extra: 01b8af2c241c78fa9d315b1ae27406aab9faecd34b49bd81bee61e696681314f3b0211000000041f90517a000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: d73e99d751f6ea7fea3e8d7b445ac504400d0f6dc2f4b8f506b6f3fe9a81b33a 0.000600000000 1770500 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": 1283093, "vin": [ { "gen": { "height": 1283083 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d73e99d751f6ea7fea3e8d7b445ac504400d0f6dc2f4b8f506b6f3fe9a81b33a" } } ], "extra": [ 1, 184, 175, 44, 36, 28, 120, 250, 157, 49, 91, 26, 226, 116, 6, 170, 185, 250, 236, 211, 75, 73, 189, 129, 190, 230, 30, 105, 102, 129, 49, 79, 59, 2, 17, 0, 0, 0, 4, 31, 144, 81, 122, 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: