Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 28f35675fc3d8cfd3317f73277f7f1892782d9c5ff30650e6b8e9687b565ba22

Tx prefix hash: ca95e07552bbbea501b8ccad77562f86b265eb5692a4bceda397fb1b23102088
Tx public key: 1e85e09b9132c0d4c0a17273c1bff500554c815c4dd7744f260f366e7ff8b569
Timestamp: 1719911790 Timestamp [UTC]: 2024-07-02 09:16:30 Age [y:d:h:m:s]: 02:057:10:48:19
Block: 1056827 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 566279 RingCT/type: yes/0
Extra: 011e85e09b9132c0d4c0a17273c1bff500554c815c4dd7744f260f366e7ff8b5690211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 97a729868509dbe0affe7f72dd665128cd2160122e83a57b02f0e2af67812d9b 0.000600000000 1527256 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": 1056837, "vin": [ { "gen": { "height": 1056827 } } ], "vout": [ { "amount": 600000000, "target": { "key": "97a729868509dbe0affe7f72dd665128cd2160122e83a57b02f0e2af67812d9b" } } ], "extra": [ 1, 30, 133, 224, 155, 145, 50, 192, 212, 192, 161, 114, 115, 193, 191, 245, 0, 85, 76, 129, 92, 77, 215, 116, 79, 38, 15, 54, 110, 127, 248, 181, 105, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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: