Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d6f7efa8345b2d77990820d4f635e8ee733954ed3be6cacb194b8079c3d9ba3e

Tx prefix hash: c89f2fdc717c4646619b4f323e6062a41f7ad5860e11a3b40b19e14c29eb6ebb
Tx public key: 4538be4bbe2f334b10a681e403a97189df4c7e70fbb35a44568b3a9bb53aaf3e
Timestamp: 1710359381 Timestamp [UTC]: 2024-03-13 19:49:41 Age [y:d:h:m:s]: 02:064:20:44:00
Block: 977653 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 558353 RingCT/type: yes/0
Extra: 014538be4bbe2f334b10a681e403a97189df4c7e70fbb35a44568b3a9bb53aaf3e0211000000010011055b000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 5d1c396d60b57d87c62f3f97c727c78210cea73e023bae9cdcbadb797be59f5c 0.000600000000 1437656 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": 977663, "vin": [ { "gen": { "height": 977653 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5d1c396d60b57d87c62f3f97c727c78210cea73e023bae9cdcbadb797be59f5c" } } ], "extra": [ 1, 69, 56, 190, 75, 190, 47, 51, 75, 16, 166, 129, 228, 3, 169, 113, 137, 223, 76, 126, 112, 251, 179, 90, 68, 86, 139, 58, 155, 181, 58, 175, 62, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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: