Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b65d95cbb78deae14077f03717bf89b089c0bfdbc56b9398e8b208e742aa09bf

Tx prefix hash: a2b323c68bbd836c1a9e7084eafea30eca2401462faff86708bcd76c28320952
Tx public key: 585c4f9ff40d447a85fc6a01909590059074001f131fd8f8eb8bdfc1b18b1332
Timestamp: 1704578869 Timestamp [UTC]: 2024-01-06 22:07:49 Age [y:d:h:m:s]: 02:056:23:34:05
Block: 929686 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 560366 RingCT/type: yes/0
Extra: 01585c4f9ff40d447a85fc6a01909590059074001f131fd8f8eb8bdfc1b18b13320211000000010011055b000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 84c827f947a9c2a5b4dabf5ffe589273d8b2cf2963af612d9d0140ad8160f908 0.000600000000 1387562 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": 929696, "vin": [ { "gen": { "height": 929686 } } ], "vout": [ { "amount": 600000000, "target": { "key": "84c827f947a9c2a5b4dabf5ffe589273d8b2cf2963af612d9d0140ad8160f908" } } ], "extra": [ 1, 88, 92, 79, 159, 244, 13, 68, 122, 133, 252, 106, 1, 144, 149, 144, 5, 144, 116, 0, 31, 19, 31, 216, 248, 235, 139, 223, 193, 177, 139, 19, 50, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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