Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 463b08ba6f2de4fbf36c8a576eddf5dc5ae221af88d8fe344580bc9668436b40

Tx prefix hash: 4281bb5183a6d0874926ab9d7c4878e4de402d520a9ec924cbe6be5b7a5a4c9a
Tx public key: 8fd523d53fce9b8e70800aa3a6ddb15a71d6a3efee89797b96342d470fc15c89
Timestamp: 1794754943 Timestamp [UTC]: 2026-11-15 15:02:23 Age [y:d:h:m:s]: 00:000:12:01:25
Block: 1678969 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0820 kB
Tx version: 2 No of confirmations: 380 RingCT/type: yes/0
Extra: 018fd523d53fce9b8e70800aa3a6ddb15a71d6a3efee89797b96342d470fc15c89

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: bd4148ec8dd8fb50aeb85edb8c79ee8bacc12e35e775f31c61753465b05c4dd6 0.000600000000 2169743 of 15 <6b>

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": 1678979, "vin": [ { "gen": { "height": 1678969 } } ], "vout": [ { "amount": 600000000, "target": { "tagged_key": { "key": "bd4148ec8dd8fb50aeb85edb8c79ee8bacc12e35e775f31c61753465b05c4dd6", "view_tag": "6b" } } } ], "extra": [ 1, 143, 213, 35, 213, 63, 206, 155, 142, 112, 128, 10, 163, 166, 221, 177, 90, 113, 214, 163, 239, 238, 137, 121, 123, 150, 52, 45, 71, 15, 193, 92, 137 ], "rct_signatures": { "type": 0 } }


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