Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b699cecf4df1cadf182c0a2995ad2175bc9a46ee6ca89d2e4c743c0e22fd3a92

Tx prefix hash: 553bb091fabe10d677a4fe76d2db57d8a12ffcaf6e362965ce4fca7fdaabde0a
Tx public key: 7794d0e98a0d6be3c101cf3673b3d941f21f4c2b627f03f1c105792a2e555f15
Timestamp: 1744379118 Timestamp [UTC]: 2025-04-11 13:45:18 Age [y:d:h:m:s]: 01:070:00:23:32
Block: 1259176 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 304712 RingCT/type: yes/0
Extra: 017794d0e98a0d6be3c101cf3673b3d941f21f4c2b627f03f1c105792a2e555f15021100000001a11dba98000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 9e711c570b896e4ef3f6f208d3b30edad7033d90fc266824700fa8d1390fb463 0.000600000000 1746315 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": 1259186, "vin": [ { "gen": { "height": 1259176 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9e711c570b896e4ef3f6f208d3b30edad7033d90fc266824700fa8d1390fb463" } } ], "extra": [ 1, 119, 148, 208, 233, 138, 13, 107, 227, 193, 1, 207, 54, 115, 179, 217, 65, 242, 31, 76, 43, 98, 127, 3, 241, 193, 5, 121, 42, 46, 85, 95, 21, 2, 17, 0, 0, 0, 1, 161, 29, 186, 152, 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: