Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2bb6e87cce95f4a5877a9383cdf8ea77c54d518cfaf114f26206455c08050394

Tx prefix hash: 85c7c073b88dd153f061cbf90768357e70e817d43f9b9c94bf02b504c6c8b98e
Tx public key: 10f8ea0ee8b44a780f639632fac1062bc09aeb395faca6279ac41911b5cb8ea8
Timestamp: 1775189155 Timestamp [UTC]: 2026-04-03 04:05:55 Age [y:d:h:m:s]: 00:231:04:35:29
Block: 1511683 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 170864 RingCT/type: yes/0
Extra: 0110f8ea0ee8b44a780f639632fac1062bc09aeb395faca6279ac41911b5cb8ea8021100000002ee4b7181000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: d2ed626b293f8992bb2dec4d23bd34f8ebe2a164de44feaefe1e5466372944d7 0.000600000000 2001477 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": 1511693, "vin": [ { "gen": { "height": 1511683 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d2ed626b293f8992bb2dec4d23bd34f8ebe2a164de44feaefe1e5466372944d7" } } ], "extra": [ 1, 16, 248, 234, 14, 232, 180, 74, 120, 15, 99, 150, 50, 250, 193, 6, 43, 192, 154, 235, 57, 95, 172, 166, 39, 154, 196, 25, 17, 181, 203, 142, 168, 2, 17, 0, 0, 0, 2, 238, 75, 113, 129, 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: