Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 648aa720d806f66babd0c0f78071f6c2ee0972763fa78cd3ce94fce7d9952f89

Tx prefix hash: 8374261ca7d47968f848fd92fb846a19aca2ec0c710218fcba6942689efc2f2e
Tx public key: fe7a13eafa8071d7482d71e24e2d0f13863aef37ae27352636580a5027253331
Timestamp: 1728206769 Timestamp [UTC]: 2024-10-06 09:26:09 Age [y:d:h:m:s]: 02:041:11:24:14
Block: 1125600 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 554291 RingCT/type: yes/0
Extra: 01fe7a13eafa8071d7482d71e24e2d0f13863aef37ae27352636580a502725333102110000000291e13c04000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: f3f9bb88ae2734bf0ed60d34048f00e46b08b8f5601a3bb270e177047fbe4ba9 0.000600000000 1608351 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": 1125610, "vin": [ { "gen": { "height": 1125600 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f3f9bb88ae2734bf0ed60d34048f00e46b08b8f5601a3bb270e177047fbe4ba9" } } ], "extra": [ 1, 254, 122, 19, 234, 250, 128, 113, 215, 72, 45, 113, 226, 78, 45, 15, 19, 134, 58, 239, 55, 174, 39, 53, 38, 54, 88, 10, 80, 39, 37, 51, 49, 2, 17, 0, 0, 0, 2, 145, 225, 60, 4, 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: