Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 515c3831172fbe67d8d9736cdf73c2b4d6fdf8cd14a6b4a32b09d21e24158cce

Tx prefix hash: a89d05382863a7a8a9e896d37d3c4b6d4a0c3b17f1729f2f770fa1fae84a6ed7
Tx public key: 0f34bd9ff4d4e6f694159ba4105ce96ad6d53d16f5ac0636ce403b1e703f6eaf
Timestamp: 1758528193 Timestamp [UTC]: 2025-09-22 08:03:13 Age [y:d:h:m:s]: 01:061:03:49:00
Block: 1373864 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 309630 RingCT/type: yes/0
Extra: 010f34bd9ff4d4e6f694159ba4105ce96ad6d53d16f5ac0636ce403b1e703f6eaf021100000001b2f784c4000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: fe0ffa9001532c55d11c95f4d28d36144842392580557251b13a16ad74336d58 0.000600000000 1861949 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": 1373874, "vin": [ { "gen": { "height": 1373864 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fe0ffa9001532c55d11c95f4d28d36144842392580557251b13a16ad74336d58" } } ], "extra": [ 1, 15, 52, 189, 159, 244, 212, 230, 246, 148, 21, 155, 164, 16, 92, 233, 106, 214, 213, 61, 22, 245, 172, 6, 54, 206, 64, 59, 30, 112, 63, 110, 175, 2, 17, 0, 0, 0, 1, 178, 247, 132, 196, 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: