Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: da6a5d7b6fdc071292ea1323e6893a5d003b2f39a108f57cc262e6f58f6a8bd0

Tx prefix hash: 42be19ac426aa4147b94357e51ed6512acb4a289e5c7d76968bdfb9a6279669c
Tx public key: b2893a6319859c5db7ebb0b7d1643654f87d2134771da1d960e7377e02c5cc5a
Timestamp: 1747741317 Timestamp [UTC]: 2025-05-20 11:41:57 Age [y:d:h:m:s]: 00:359:07:20:15
Block: 1287006 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 246804 RingCT/type: yes/0
Extra: 01b2893a6319859c5db7ebb0b7d1643654f87d2134771da1d960e7377e02c5cc5a02110000000a9f9fe68c000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 41a9a406c93a45888d9f66618d0ec10c5ed4fb37c8fe6183e7b9db15f6d5e12a 0.000600000000 1774473 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": 1287016, "vin": [ { "gen": { "height": 1287006 } } ], "vout": [ { "amount": 600000000, "target": { "key": "41a9a406c93a45888d9f66618d0ec10c5ed4fb37c8fe6183e7b9db15f6d5e12a" } } ], "extra": [ 1, 178, 137, 58, 99, 25, 133, 156, 93, 183, 235, 176, 183, 209, 100, 54, 84, 248, 125, 33, 52, 119, 29, 161, 217, 96, 231, 55, 126, 2, 197, 204, 90, 2, 17, 0, 0, 0, 10, 159, 159, 230, 140, 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: