Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 99eff3c9a307e14d16400102d57ce7cb116e3bb7fbad3de3d2d26b0cdd314fab

Tx prefix hash: 741d7b9e541c2bd5d0bdfacc5b02542782f062c53bbe89207c9bee6c7a614217
Tx public key: ce8fcec6173584ae4596bbefc103395f26dc6fd8cf946f74e5e552ae3bbf7d4a
Timestamp: 1730309111 Timestamp [UTC]: 2024-10-30 17:25:11 Age [y:d:h:m:s]: 02:022:10:19:16
Block: 1142943 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 540551 RingCT/type: yes/0
Extra: 01ce8fcec6173584ae4596bbefc103395f26dc6fd8cf946f74e5e552ae3bbf7d4a021100000001007f978a000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 4740e0c8c90f71841c08e89fcf4add069ef38bbd1ad11aeff70a4b7c5cbd6e6c 0.000600000000 1626800 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": 1142953, "vin": [ { "gen": { "height": 1142943 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4740e0c8c90f71841c08e89fcf4add069ef38bbd1ad11aeff70a4b7c5cbd6e6c" } } ], "extra": [ 1, 206, 143, 206, 198, 23, 53, 132, 174, 69, 150, 187, 239, 193, 3, 57, 95, 38, 220, 111, 216, 207, 148, 111, 116, 229, 229, 82, 174, 59, 191, 125, 74, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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: