Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5c42b30ea593460c4b4c7d24d52b4429d8ca74c1d931f39f7b04fbadd7c2b6d3

Tx prefix hash: 3d806611ac085d542823e83270cb905d87da250ea316463b7fa8cfd0e1656376
Tx public key: 780c15848e3ee859a10faad0c4cf30e050e7362d3c90ca58f426c0d2fa021889
Timestamp: 1716848947 Timestamp [UTC]: 2024-05-27 22:29:07 Age [y:d:h:m:s]: 01:356:12:47:06
Block: 1031444 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 506778 RingCT/type: yes/0
Extra: 01780c15848e3ee859a10faad0c4cf30e050e7362d3c90ca58f426c0d2fa0218890211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 6b0baeaa7623fd230c4a0ee5d96d66fbb5ed5e06305d12bf878ea91dfe98290e 0.000600000000 1499889 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": 1031454, "vin": [ { "gen": { "height": 1031444 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6b0baeaa7623fd230c4a0ee5d96d66fbb5ed5e06305d12bf878ea91dfe98290e" } } ], "extra": [ 1, 120, 12, 21, 132, 142, 62, 232, 89, 161, 15, 170, 208, 196, 207, 48, 224, 80, 231, 54, 45, 60, 144, 202, 88, 244, 38, 192, 210, 250, 2, 24, 137, 2, 17, 0, 0, 0, 4, 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: