Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d7ca6bf46b1945d56499ddc15f92b5a3f7193ac4ccf520dc01a91fb03d4e6962

Tx prefix hash: 08da834bb7e36189a0e92a5e9bed1c37196f7997dbce9f0d0c51657571ff8c90
Tx public key: 1f7f76f37ae180fb2e3a70b21d48fb112e29e65e534910ff6c39f6041fdce60a
Timestamp: 1772658411 Timestamp [UTC]: 2026-03-04 21:06:51 Age [y:d:h:m:s]: 00:262:16:02:40
Block: 1490752 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 192742 RingCT/type: yes/0
Extra: 011f7f76f37ae180fb2e3a70b21d48fb112e29e65e534910ff6c39f6041fdce60a021100000003e4f5193f000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: bb32600a3daffecd5df2b7ff35adff26b017b773fb37d58b7b0cb3fbb0d18008 0.000600000000 1980262 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": 1490762, "vin": [ { "gen": { "height": 1490752 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bb32600a3daffecd5df2b7ff35adff26b017b773fb37d58b7b0cb3fbb0d18008" } } ], "extra": [ 1, 31, 127, 118, 243, 122, 225, 128, 251, 46, 58, 112, 178, 29, 72, 251, 17, 46, 41, 230, 94, 83, 73, 16, 255, 108, 57, 246, 4, 31, 220, 230, 10, 2, 17, 0, 0, 0, 3, 228, 245, 25, 63, 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: