Dinastycoin Explorer Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1bddb534b89a5401befe23ddfebfdf67493b3be2d47c8cc59291a720b709d2fb

Tx prefix hash: 04609e65bb0d33b3dc4b1bdff75294fb5d2c1f7d60128fa27f4c7249df95a207
Tx public key: 8e990ace5ea070cca5890a7ab420f10d5f06ce15dd6c0068c1c495c00b8f922e
Timestamp: 1783279240 Timestamp [UTC]: 2026-07-05 19:20:40 Age [y:d:h:m:s]: 00:009:11:09:40
Block: 1575438 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0918 kB
Tx version: 2 No of confirmations: 7271 RingCT/type: yes/0
Extra: 018e990ace5ea070cca5890a7ab420f10d5f06ce15dd6c0068c1c495c00b8f922e02080421ec1286fcac15

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: f33fbd5c6f65033e3d884f31458e56f54f714e90858f55f9096a3cf822dc08e5 0.000600000000 2065420 of 15 <70>

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": 1575448, "vin": [ { "gen": { "height": 1575438 } } ], "vout": [ { "amount": 600000000, "target": { "tagged_key": { "key": "f33fbd5c6f65033e3d884f31458e56f54f714e90858f55f9096a3cf822dc08e5", "view_tag": "70" } } } ], "extra": [ 1, 142, 153, 10, 206, 94, 160, 112, 204, 165, 137, 10, 122, 180, 32, 241, 13, 95, 6, 206, 21, 221, 108, 0, 104, 193, 196, 149, 192, 11, 143, 146, 46, 2, 8, 4, 33, 236, 18, 134, 252, 172, 21 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): devel-2026-02-02-6303d2a (1.2) | monero version: