Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b07d916d8d2ec3886c92e850a3d30c0956cef74354fe7e2b0694167671b8f9a6

Tx prefix hash: 1039a95e88f55cdd773f32d524225e9859c9bfe531ae77fa168ec51900a5a0dd
Tx public key: 0ef606fb2dc507d41b277c1ed8b40a0aca3666e6de0a21bafb3e084f064239d7
Timestamp: 1768587245 Timestamp [UTC]: 2026-01-16 18:14:05 Age [y:d:h:m:s]: 00:029:06:40:00
Block: 1457089 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 20902 RingCT/type: yes/0
Extra: 010ef606fb2dc507d41b277c1ed8b40a0aca3666e6de0a21bafb3e084f064239d7021100000005215bbf89000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: cf3a56f1e3f68ff544ec7de5a78cb7024b5f0b9e665647f54cd3b57a1eb34da7 0.000600000000 1946213 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": 1457099, "vin": [ { "gen": { "height": 1457089 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cf3a56f1e3f68ff544ec7de5a78cb7024b5f0b9e665647f54cd3b57a1eb34da7" } } ], "extra": [ 1, 14, 246, 6, 251, 45, 197, 7, 212, 27, 39, 124, 30, 216, 180, 10, 10, 202, 54, 102, 230, 222, 10, 33, 186, 251, 62, 8, 79, 6, 66, 57, 215, 2, 17, 0, 0, 0, 5, 33, 91, 191, 137, 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