Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a58d7c24498c367645cab35eb546a27c8b29aaf85ff6f406b3cede3a185ab657

Tx prefix hash: 02f751c94e7c8739077f44a37483446aa4978f04ffb3491d90fa34ec442a0dd1
Tx public key: 095aa341faabde4c155cc4a5753f25626836d9daaeb126926e9c796512c615b0
Timestamp: 1711452330 Timestamp [UTC]: 2024-03-26 11:25:30 Age [y:d:h:m:s]: 02:238:02:48:52
Block: 986716 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 695229 RingCT/type: yes/0
Extra: 01095aa341faabde4c155cc4a5753f25626836d9daaeb126926e9c796512c615b002110000000452d47e94000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 6dea527a15304d3fc8f3eb3d48f0a603797e9d171e48007e096a4693ecdab2c4 0.000600000000 1446949 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": 986726, "vin": [ { "gen": { "height": 986716 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6dea527a15304d3fc8f3eb3d48f0a603797e9d171e48007e096a4693ecdab2c4" } } ], "extra": [ 1, 9, 90, 163, 65, 250, 171, 222, 76, 21, 92, 196, 165, 117, 63, 37, 98, 104, 54, 217, 218, 174, 177, 38, 146, 110, 156, 121, 101, 18, 198, 21, 176, 2, 17, 0, 0, 0, 4, 82, 212, 126, 148, 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: