Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7ca1cbdda18b9195e2e0ee6f9cbb36e21fe12878d42b7e55e9e56171ad428ee4

Tx prefix hash: f22436cdd4c09320b85c301adb75dcc6eb6780b0ea1e6f3c2225d19f372415ac
Tx public key: 6f4387ac3e4a59737ab0dce8d4508d7fd93e5738d397aab5c79fc3ef0490f572
Timestamp: 1717453378 Timestamp [UTC]: 2024-06-03 22:22:58 Age [y:d:h:m:s]: 02:170:10:22:10
Block: 1036449 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 646844 RingCT/type: yes/0
Extra: 016f4387ac3e4a59737ab0dce8d4508d7fd93e5738d397aab5c79fc3ef0490f57202110000000159dad3f5000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 274c79458f7aa55f031716906169cdc282870df62c77bf084c1bf347061b859f 0.000600000000 1504976 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": 1036459, "vin": [ { "gen": { "height": 1036449 } } ], "vout": [ { "amount": 600000000, "target": { "key": "274c79458f7aa55f031716906169cdc282870df62c77bf084c1bf347061b859f" } } ], "extra": [ 1, 111, 67, 135, 172, 62, 74, 89, 115, 122, 176, 220, 232, 212, 80, 141, 127, 217, 62, 87, 56, 211, 151, 170, 181, 199, 159, 195, 239, 4, 144, 245, 114, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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: