Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: efeb50ddda3ec9e37ae7b1fbe6728d2e11677412b6077c4a27e11ad0ec46eafb

Tx prefix hash: eb6375f3c8318cf274a99825faa4c3d5336d9f50d0aeea3572cce496862a85aa
Tx public key: 20e61ae50006c1d533227a4b7225a80013ba3cc1561f90fa01da1ffa4171ee3b
Timestamp: 1751433275 Timestamp [UTC]: 2025-07-02 05:14:35 Age [y:d:h:m:s]: 00:242:06:03:55
Block: 1317019 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 171289 RingCT/type: yes/0
Extra: 0120e61ae50006c1d533227a4b7225a80013ba3cc1561f90fa01da1ffa4171ee3b02110000000101491f88000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 11b597b3859571e6ec33b30d0eb519adcddc7c82d2a95e258cf19e3b5372ac7e 0.000600000000 1804684 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": 1317029, "vin": [ { "gen": { "height": 1317019 } } ], "vout": [ { "amount": 600000000, "target": { "key": "11b597b3859571e6ec33b30d0eb519adcddc7c82d2a95e258cf19e3b5372ac7e" } } ], "extra": [ 1, 32, 230, 26, 229, 0, 6, 193, 213, 51, 34, 122, 75, 114, 37, 168, 0, 19, 186, 60, 193, 86, 31, 144, 250, 1, 218, 31, 250, 65, 113, 238, 59, 2, 17, 0, 0, 0, 1, 1, 73, 31, 136, 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) | dinastycoin version: tesla-369