Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dee44096788da1dd89a564e73afd91ff49f6ed10ec8fffb44491d9074132efe4

Tx prefix hash: 4dc2a017f1e52be6d643ea5f55a8ebc1a1fe2e096ea369ccbd4d05a7daf27231
Tx public key: 6397aae3a6b13a07553f989d7b36d801016addeff8ef6ac7869eaa1c9349b60a
Timestamp: 1787402584 Timestamp [UTC]: 2026-08-22 12:43:04 Age [y:d:h:m:s]: 00:091:01:16:23
Block: 1618929 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0918 kB
Tx version: 2 No of confirmations: 64524 RingCT/type: yes/0
Extra: 016397aae3a6b13a07553f989d7b36d801016addeff8ef6ac7869eaa1c9349b60a0208cd687445167a9f90

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: b6f417255bc1d108cb4c2913bf11a6936a1068ed860edcd31df3ed6b890cad5c 0.000600000000 2108949 of 15 <6d>

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": 1618939, "vin": [ { "gen": { "height": 1618929 } } ], "vout": [ { "amount": 600000000, "target": { "tagged_key": { "key": "b6f417255bc1d108cb4c2913bf11a6936a1068ed860edcd31df3ed6b890cad5c", "view_tag": "6d" } } } ], "extra": [ 1, 99, 151, 170, 227, 166, 177, 58, 7, 85, 63, 152, 157, 123, 54, 216, 1, 1, 106, 221, 239, 248, 239, 106, 199, 134, 158, 170, 28, 147, 73, 182, 10, 2, 8, 205, 104, 116, 69, 22, 122, 159, 144 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): devel-2026-02-02-6303d2a (1.2) | monero version: