Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f9e866e64d83705f1f4ba4bf89c4daafb8dde79d934d71dc02ca0af715bf3ef1

Tx prefix hash: be312fd5d29fbe33dec39ebf705e5b469f612c81444e87ec5a3f646de769408a
Tx public key: 0e267290518dcd5c7c1ca4c66a123ffc45dd5a6e4506c6c4e79acf77cad86037
Timestamp: 1756397204 Timestamp [UTC]: 2025-08-28 16:06:44 Age [y:d:h:m:s]: 01:084:04:30:42
Block: 1356387 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 326535 RingCT/type: yes/0
Extra: 010e267290518dcd5c7c1ca4c66a123ffc45dd5a6e4506c6c4e79acf77cad860370211000000032609b3a0000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: c5edc2538fda1d0309e1b1b9f03b70d83779a09c152ffc603cbeeda5170394cf 0.000600000000 1844396 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": 1356397, "vin": [ { "gen": { "height": 1356387 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c5edc2538fda1d0309e1b1b9f03b70d83779a09c152ffc603cbeeda5170394cf" } } ], "extra": [ 1, 14, 38, 114, 144, 81, 141, 205, 92, 124, 28, 164, 198, 106, 18, 63, 252, 69, 221, 90, 110, 69, 6, 198, 196, 231, 154, 207, 119, 202, 216, 96, 55, 2, 17, 0, 0, 0, 3, 38, 9, 179, 160, 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: