Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 350f78903f6b817b81e2e6d8314f2e69f70adf361e9e230373df0ea830ad44c3

Tx prefix hash: a8fc65d33d0ff35d72219b28b91abf42704f15d98902e5bdef88cc4f8dfc6ceb
Tx public key: ba3a54be24198f7be45a03599d0615bba8626e00dae3eddb53b6e43980d4e8fd
Timestamp: 1657193272 Timestamp [UTC]: 2022-07-07 11:27:52 Age [y:d:h:m:s]: 04:138:20:55:50
Block: 538569 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 1144925 RingCT/type: yes/0
Extra: 01ba3a54be24198f7be45a03599d0615bba8626e00dae3eddb53b6e43980d4e8fd02110000000375e3f0e9000000000000000000

1 output(s) for total of 0.010080857631 xmr

stealth address amount amount idx tag
00: 014176814d3e6279b25a446c686d22a5e478415cabddf60718b162702b0d9508 0.010080857631 968584 of 0 -

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": 538579, "vin": [ { "gen": { "height": 538569 } } ], "vout": [ { "amount": 10080857631, "target": { "key": "014176814d3e6279b25a446c686d22a5e478415cabddf60718b162702b0d9508" } } ], "extra": [ 1, 186, 58, 84, 190, 36, 25, 143, 123, 228, 90, 3, 89, 157, 6, 21, 187, 168, 98, 110, 0, 218, 227, 237, 219, 83, 182, 228, 57, 128, 212, 232, 253, 2, 17, 0, 0, 0, 3, 117, 227, 240, 233, 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: