Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1b5493f400cef46aba21704e4c5824ef1a3555f92929954ab2bca86c6e36e6b3

Tx prefix hash: a2f42d986d3d55b909f0a6e9e1cae2ddf57aa72f37ca4aa58f8ae150d67d7ecc
Tx public key: 0fb313e4d4bd242d0df5c39d486b8cac601912340196e273efb871c2e786b722
Timestamp: 1711574449 Timestamp [UTC]: 2024-03-27 21:20:49 Age [y:d:h:m:s]: 02:051:08:42:59
Block: 987722 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 548737 RingCT/type: yes/0
Extra: 010fb313e4d4bd242d0df5c39d486b8cac601912340196e273efb871c2e786b72202110000000159dad3f5000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 11be4869ac50d966fc90883bebeb1380fb284a3dc18e8000e8ce9fd71b126db0 0.000600000000 1447979 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": 987732, "vin": [ { "gen": { "height": 987722 } } ], "vout": [ { "amount": 600000000, "target": { "key": "11be4869ac50d966fc90883bebeb1380fb284a3dc18e8000e8ce9fd71b126db0" } } ], "extra": [ 1, 15, 179, 19, 228, 212, 189, 36, 45, 13, 245, 195, 157, 72, 107, 140, 172, 96, 25, 18, 52, 1, 150, 226, 115, 239, 184, 113, 194, 231, 134, 183, 34, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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: