Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2bb7d963aa9db5498b8318ca21ec4c7e38f7769fd241918a1b1346f2d66561ba

Tx prefix hash: f6db5d11066e66f4fb58cacab3fa6072a5799843393d512c72d7efb43541c48e
Tx public key: ee579c6e86c4be9b7064a5db8081f4ee7f0fa29c5b5c00d4256064431fae0d4c
Timestamp: 1657028619 Timestamp [UTC]: 2022-07-05 13:43:39 Age [y:d:h:m:s]: 04:139:23:00:54
Block: 537206 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 1146201 RingCT/type: yes/0
Extra: 01ee579c6e86c4be9b7064a5db8081f4ee7f0fa29c5b5c00d4256064431fae0d4c0211000000014da16a3a000000000000000000

1 output(s) for total of 0.010186234459 xmr

stealth address amount amount idx tag
00: 84510a2a8ea57fa8450601d352350c1f9ed6e9bd535e2517960a25835f5ca1e2 0.010186234459 967069 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": 537216, "vin": [ { "gen": { "height": 537206 } } ], "vout": [ { "amount": 10186234459, "target": { "key": "84510a2a8ea57fa8450601d352350c1f9ed6e9bd535e2517960a25835f5ca1e2" } } ], "extra": [ 1, 238, 87, 156, 110, 134, 196, 190, 155, 112, 100, 165, 219, 128, 129, 244, 238, 127, 15, 162, 156, 91, 92, 0, 212, 37, 96, 100, 67, 31, 174, 13, 76, 2, 17, 0, 0, 0, 1, 77, 161, 106, 58, 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: