Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e22e55518feb5e50e1e99faeab53843ac9f2302024dfa81f49a1aa2c8e388071

Tx prefix hash: aa4d90614ff294f23bd1e095a50ab07c0fe7e4ad90dc31a4e71ae4af3d5d39bf
Tx public key: 0049e9c2a1d63040b4408865466e54ed382c2983956e12ba4ba37162ad206425
Timestamp: 1648879229 Timestamp [UTC]: 2022-04-02 06:00:29 Age [y:d:h:m:s]: 04:233:21:46:53
Block: 471433 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 1211709 RingCT/type: yes/0
Extra: 010049e9c2a1d63040b4408865466e54ed382c2983956e12ba4ba37162ad206425021100000003bf7ee4e7000000000000000000

1 output(s) for total of 0.016824687918 xmr

stealth address amount amount idx tag
00: d9a75f87bf7e0c0c77b964e1b5a78f389441b58ab7d7fcae98c2d81db1701d60 0.016824687918 890777 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": 471443, "vin": [ { "gen": { "height": 471433 } } ], "vout": [ { "amount": 16824687918, "target": { "key": "d9a75f87bf7e0c0c77b964e1b5a78f389441b58ab7d7fcae98c2d81db1701d60" } } ], "extra": [ 1, 0, 73, 233, 194, 161, 214, 48, 64, 180, 64, 136, 101, 70, 110, 84, 237, 56, 44, 41, 131, 149, 110, 18, 186, 75, 163, 113, 98, 173, 32, 100, 37, 2, 17, 0, 0, 0, 3, 191, 126, 228, 231, 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: